tmobile/jazz

Executive summary

tmobile/jazz scores 51 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 45 and is rated Weak. Its Secret Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 3 Leaked secret finding(s) in Secret Scanning and to resolve the 2 Assertions commented out finding(s) in Test Quality, and if Production Readiness rose to 70, the score would rise from 51 to about 56.

76 findings are critical: 40 in Dependency Vulnerabilities, 13 in Dependency Hygiene, 13 in Secrets (history), five in Static Analysis (SAST), three in Secret Scanning and two in Test Quality.

Watchdog couldn't measure 11 dimensions in this code, among them Dependency Hygiene, Navigability and IL Efficiency, so they are left out of the score. The product code is 55,571 lines, which would take an estimated 0.6 person-years, around €82,000, to rebuild.

Code Health 50 Weak, capped by Type Safety and Nullable reference types Architecture 65 Adequate, capped by Code composition Maturity 63 Adequate, capped by Knowledge Freshness Production Readiness 45 Weak, capped by Test Distribution, Secret Scanning and Dependency Hygiene Security and Compliance 59 Adequate, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities and Malicious Dependencies Performance 60 Adequate

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.

Production Readiness 45 · counts for 46%Code Health 50 · counts for 25%Security and Compliance 59 · counts for 14%Performance 60 · counts for 8%Maturity 63 · counts for 4%Architecture 65 · counts for 2%

If Production Readiness rose from 45 to 70, the lowest score rated Strong, the score would rise from 51 to about 56.

Code composition: what the lines of code are

Product code 67%Tests 33%

New since the last survey: 102 findings

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

Cyclomatic Complexity · create.default::getServiceData (cyclomatic 23) core/jazz_create-serverless-service/components/crud/create.js
Cyclomatic Complexity · update.default::getServiceData (cyclomatic 19) core/jazz_services-handler/components/crud/update.js
Cognitive Complexity · create.default::getServiceData (cognitive 26) core/jazz_create-serverless-service/components/crud/create.js
Cognitive Complexity · update.default::getServiceData (cognitive 22) core/jazz_services-handler/components/crud/update.js
Cognitive Complexity · update.default::getServiceData (cognitive 18) core/jazz_create-serverless-service/components/crud/update.js
Secret Scanning · REDACTED
Secret Scanning · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Supply-chain Provenance & Signing · REDACTED
Large Files · core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts: 1376 lines of code core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts
Large Files · REDACTED: 1172 lines of code REDACTED
Large Files · REDACTED: 824 lines of code REDACTED
Large Files · core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts: 796 lines of code core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts
Large Files · core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts: 774 lines of code core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts
Large Files · core/jazz_metrics/index.js: 730 lines of code core/jazz_metrics/index.js
Large Files · core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts: 717 lines of code core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts
Large Files · core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts: 710 lines of code core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts
Large Files · core/jazz_ui/src/app/pages/services-list/services-list.component.ts: 676 lines of code core/jazz_ui/src/app/pages/services-list/services-list.component.ts
Large Files · core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts: 599 lines of code core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts
Large Files · core/jazz_environment-event-handler/index.js: 595 lines of code core/jazz_environment-event-handler/index.js
Large Files · core/jazz_t-vault/components/utils/vault.js: 555 lines of code core/jazz_t-vault/components/utils/vault.js
Large Files · core/jazz_deployments/index.js: 552 lines of code core/jazz_deployments/index.js
Large Files · core/jazz_create-serverless-service/index.js: 518 lines of code core/jazz_create-serverless-service/index.js
Large Files · core/jazz_slack-channel/index.js: 504 lines of code core/jazz_slack-channel/index.js
Large Files · REDACTED: 502 lines of code REDACTED
Large Files · REDACTED: 459 lines of code REDACTED
Large Files · core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts: 455 lines of code core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts
Large Files · REDACTED: 453 lines of code REDACTED
Large Files · core/jazz_token-authorizer/index.js: 444 lines of code core/jazz_token-authorizer/index.js
Large Files · core/jazz_usermanagement/index.js: 437 lines of code core/jazz_usermanagement/index.js
Large Files · REDACTED: 424 lines of code REDACTED
Large Files · core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts: 414 lines of code core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts
Large Files · core/jazz_metrics/components/utils.js: 405 lines of code core/jazz_metrics/components/utils.js
Large Files · core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts: 402 lines of code core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts
Tooling · No typecheck script
Dependency Hygiene · Unlisted import 'aws-sdk' core/jazz_admin/components/utils.js
Exception handling · Swallowed exception (empty catch) core/jazz_acl/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_admin/components/utils.js
Exception handling · Swallowed exception (empty catch) core/jazz_admin/components/utils.js
Exception handling · Swallowed exception (empty catch) core/jazz_admin/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_apigee-proxy-aws/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_asset-event-handler/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_assets/components/utils.js
Exception handling · Swallowed exception (empty catch) core/jazz_assets/components/utils.js
Exception handling · Swallowed exception (empty catch) core/jazz_assets/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_cloud-logs-streamer/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_codeq/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_cognito-admin-authorizer/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_cognito-authorizer/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_create-serverless-service/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_delete-serverless-service/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_deployments-event-handler/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_deployments/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_email/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_environment-event-handler/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_environments/components/utils.js
Exception handling · Swallowed exception (empty catch) core/jazz_environments/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_es-kinesis-log-streamer/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_events-handler/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_events/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_is-service-available/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_is-slack-channel-available/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_login/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_logout/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_logs/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_metrics/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_scm-webhook/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_services-handler/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_services/components/utils.js
Exception handling · Swallowed exception (empty catch) core/jazz_services/components/utils.js
Exception handling · Swallowed exception (empty catch) core/jazz_services/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_slack-channel/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_slack-event-handler/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_splunk-kinesis-log-streamer/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_t-vault/components/logger.js
Exception handling · Swallowed exception (empty catch) core/jazz_token-authorizer/components/logger.js
Incompleteness & stubs · Both branches are identical — the condition decides nothing core/jazz_services/components/utils.js
Incompleteness & stubs · Both branches are identical — the condition decides nothing core/jazz_ui/src/app/core/services/request.service.ts
Incompleteness & stubs · Both branches are identical — the condition decides nothing core/jazz_ui/src/app/core/services/request.service.ts
Incompleteness & stubs · Both branches are identical — the condition decides nothing core/jazz_ui/src/app/core/services/request.service.ts
Async & latency hygiene · Sync-over-async blocking REDACTED

Watchdog compares 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: 336 findings

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

Cyclomatic Complexity · create.default (cyclomatic 26) core/jazz_create-serverless-service/components/crud/create.js
Cyclomatic Complexity · update.default (cyclomatic 22) core/jazz_services-handler/components/crud/update.js
Cognitive Complexity · create.default (cognitive 29) core/jazz_create-serverless-service/components/crud/create.js
Cognitive Complexity · update.default (cognitive 25) core/jazz_services-handler/components/crud/update.js
Cognitive Complexity · update.default (cognitive 22) core/jazz_create-serverless-service/components/crud/update.js
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Supply-chain Provenance & Signing REDACTED
Code Duplication · Duplicated block (34 lines × 5 locations) core/jazz_assets/components/error-handler.js
Code Duplication · Duplicated block (34 lines × 2 locations) core/jazz_assets/components/utils.js
Code Duplication · Duplicated block (34 lines × 2 locations) core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts
Code Duplication · Duplicated block with local edits (31 matched lines × 2 locations) builds/jazz_azure-create-service/components/ApiApp.js
Code Duplication · Duplicated block (31 lines × 2 locations) core/jazz_acl/components/utils/vault.js
Code Duplication · Duplicated block (31 lines × 3 locations) core/jazz_asset-event-handler/components/config.js
Code Duplication · Duplicated block (31 lines × 3 locations) REDACTED
Code Duplication · Duplicated block (31 lines × 2 locations) core/jazz_es-kinesis-log-streamer/components/config.js
Code Duplication · Duplicated block (31 lines × 2 locations) core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts
Code Duplication · Duplicated block (31 lines × 2 locations) core/jazz_ui/src/app/pages/landing/landing.component.ts
Code Duplication · Duplicated block (29 lines × 2 locations) builds/jazz_azure-create-service/components/function/eventhubHandler.js
Code Duplication · Duplicated block (29 lines × 25 locations) core/jazz_admin/components/config.js
Code Duplication · Duplicated block (29 lines × 2 locations) core/jazz_create-serverless-service/components/crud/create.js
Code Duplication · Duplicated block (29 lines × 2 locations) templates/azure-api-template-nodejs/components/config.js
Code Duplication · Duplicated block (28 lines × 2 locations) core/jazz_ui/src/app/core/services/request.service.ts
Code Duplication · Duplicated block (28 lines × 2 locations) core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts
Code Duplication · Duplicated block (27 lines × 2 locations) core/jazz_ui/src/app/secondary-components/chartjs-linegraph/chartjs-linegraph.component.ts
Code Duplication · Duplicated block (26 lines × 9 locations) core/jazz_acl/components/config.js
Code Duplication · Duplicated block (25 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (25 lines × 11 locations) core/jazz_acl/components/error-handler.js
Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) core/jazz_scm-webhook/index.js
Code Duplication · Duplicated block (25 lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts
Code Duplication · Duplicated block (25 lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts
Code Duplication · Duplicated block (24 lines × 2 locations) core/jazz_create-serverless-service/components/cron-parser.js
Code Duplication · Duplicated block (23 lines × 3 locations) core/jazz_acl/components/scm/services.js
Code Duplication · Duplicated block with local edits (23 matched lines × 2 locations) REDACTED
Code Duplication · Duplicated block (23 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (23 lines × 2 locations) core/jazz_t-vault/components/utils/vault.js
Code Duplication · Duplicated block (22 lines × 9 locations) core/jazz_acl/components/config.js
Code Duplication · Duplicated block (22 lines × 3 locations) core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.ts
Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) core/jazz_assets/components/validation.js
Code Duplication · Duplicated block (21 lines × 2 locations) core/jazz_cognito-authorizer/index.js
Code Duplication · Duplicated block (21 lines × 2 locations) core/jazz_create-serverless-service/index.js
Code Duplication · Duplicated block (21 lines × 4 locations) core/jazz_deployments/index.js
Code Duplication · Duplicated block (21 lines × 2 locations) core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts
Code Duplication · Duplicated block (21 lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts
Code Duplication · Duplicated block (20 lines × 2 locations) core/jazz_admin/components/utils.js
Code Duplication · Duplicated block (20 lines × 2 locations) core/jazz_admin/index.js
Code Duplication · Duplicated block (20 lines × 3 locations) core/jazz_cloud-logs-streamer/components/error-handler.js
Code Duplication · Duplicated block (20 lines × 3 locations) REDACTED
Code Duplication · Duplicated block (20 lines × 2 locations) core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts
Code Duplication · Duplicated block (19 lines × 2 locations) core/jazz_admin/index.js
Code Duplication · Duplicated block (19 lines × 2 locations) core/jazz_assets/index.js
Code Duplication · Duplicated block (19 lines × 2 locations) core/jazz_environments/components/crud/get.js
Code Duplication · Duplicated block (19 lines × 2 locations) core/jazz_services/components/validation/common.js
Code Duplication · Duplicated block (19 lines × 2 locations) core/jazz_slack-event-handler/components/utils.js
Code Duplication · Duplicated block (19 lines × 2 locations) core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts
Code Duplication · Duplicated block (19 lines × 6 locations) core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts
Code Duplication · Duplicated block (19 lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts
Code Duplication · Duplicated block (18 lines × 2 locations) core/jazz_assets/components/validation.js
Code Duplication · Duplicated block (18 lines × 3 locations) core/jazz_create-serverless-service/components/crud/create.js
Code Duplication · Duplicated block (18 lines × 2 locations) core/jazz_create-serverless-service/index.js
Code Duplication · Duplicated block (18 lines × 2 locations) core/jazz_deployments/components/validation.js
Code Duplication · Duplicated block (18 lines × 3 locations) core/jazz_events/index.js
Code Duplication · Duplicated block (18 lines × 2 locations) core/jazz_ui/src/app/secondary-components/filter-tags/filter-tags.component.ts
Code Duplication · Duplicated block (17 lines × 2 locations) core/jazz_assets/components/crud/create.js
Code Duplication · Duplicated block (17 lines × 2 locations) core/jazz_assets/components/utils.js
Code Duplication · Duplicated block (17 lines × 2 locations) core/jazz_assets/components/validation.js
Code Duplication · Duplicated block (17 lines × 2 locations) core/jazz_deployments/index.js
Code Duplication · Duplicated block (17 lines × 2 locations) core/jazz_environments/index.js
Code Duplication · Duplicated block (17 lines × 3 locations) core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts
Code Duplication · Duplicated block (17 lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts
Code Duplication · Duplicated block (17 lines × 2 locations) templates/sls-app-template-nodejs/functions/function1/index.js
Code Duplication · Duplicated block (16 lines × 2 locations) builds/jazz-build-module/apigee/templates/coreAPI_default/Common/resources/jsc/cf_CORS.js
Code Duplication · Duplicated block (16 lines × 2 locations) builds/jazz_azure-create-service/components/function/functionCreateHandler.js
Code Duplication · Duplicated block (16 lines × 2 locations) core/jazz_acl/components/utils/vault.js
Code Duplication · Duplicated block (16 lines × 2 locations) core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts
Code Duplication · Duplicated block (15 lines × 4 locations) core/jazz_deployments/components/validation.js
Code Duplication · Duplicated block (15 lines × 3 locations) core/jazz_environments/components/validation/common.js
Code Duplication · Duplicated block (15 lines × 2 locations) core/jazz_environments/components/validation/validate_create_payload.js
Code Duplication · Duplicated block (15 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (15 lines × 2 locations) core/jazz_scm-webhook/index.js
Code Duplication · Duplicated block (15 lines × 3 locations) core/jazz_services/components/validation/common.js
Code Duplication · Duplicated block (15 lines × 2 locations) core/jazz_ui/karma.conf.js
Code Duplication · Duplicated block (15 lines × 2 locations) core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts
Code Duplication · Duplicated block (15 lines × 2 locations) core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts
Code Duplication · Duplicated block (15 lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts
Code Duplication · Duplicated block (14 lines × 2 locations) core/jazz_asset-event-handler/index.js
Code Duplication · Duplicated block (14 lines × 3 locations) REDACTED
Code Duplication · Duplicated block (14 lines × 2 locations) core/jazz_deployments-event-handler/components/utils.js
Code Duplication · Duplicated block (14 lines × 9 locations) core/jazz_environments/components/validation/validate_create_payload.js
Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (14 lines × 2 locations) core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts
Code Duplication · Duplicated block (14 lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts
Code Duplication · Duplicated block (14 lines × 2 locations) core/jazz_ui/src/app/secondary-components/filter-tags/filter-tags.component.ts
Code Duplication · Duplicated block (14 lines × 2 locations) core/jazz_usermanagement/index.js
Code Duplication · Duplicated block (13 lines × 2 locations) core/jazz_assets/components/validation.js
Code Duplication · Duplicated block (13 lines × 3 locations) REDACTED
Code Duplication · Duplicated block (13 lines × 2 locations) core/jazz_deployments-event-handler/index.js
Code Duplication · Duplicated block (13 lines × 3 locations) core/jazz_environments/components/validation/validate_create_payload.js
Code Duplication · Duplicated block (13 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (13 lines × 2 locations) core/jazz_metrics/index.js
Code Duplication · Duplicated block (13 lines × 4 locations) core/jazz_ui/src/app/core/services/request.service.ts

Rebuild cost: about €82,000 · Estimate

Cost to rebuild	€27,000 to €140,000, for 456 to 1,447 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 55,571 lines of product code

How the estimate is made: Watchdog prices 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.

Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED.

Raises the score by about 6 points · Low effort · Secret Scanning

Resolve the 2 Assertions commented out finding(s) in Test Quality — start with websiteservices.e2e-spec.ts (2).

Raises the score by about 3 points · Low effort · Test Quality

Improve Test Distribution — currently 3.6/10.

Raises the score by about 5 points · Medium effort · Test Distribution

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 €82,000 to build again, about 0.6 person-years of work. Its weakest lens is Production Readiness, at 45 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

If you do one thing first · First action

Resolve the 3 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 3 Secret Scanning findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

What hard-to-read code costs each year · Cost

Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.5 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 5,785 lines over the last 90 days, which is about 23,461 lines a year. At that pace, the extra work comes to an estimated 1.2 to 7.8 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 Watchdog's 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; 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.

235 modules, with 138 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; 195 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 com.slf.model	2 core.jazz_ui.src.app.SharedService_service	3 core.jazz_ui.src.app.adv-filter_directive	4 core.jazz_ui.src.app.advanced-filter_service	5 core.jazz_ui.src.app.core.helpers.cronparser_service	6 core.jazz_ui.src.app.core.services.authentication_service	7 core.jazz_ui.src.app.core.services.datacache_service	8 core.jazz_ui.src.app.core.services.message_service	9 core.jazz_ui.src.app.core.services.rename-field_service	10 core.jazz_ui.src.app.core.services.utils_service	11 core.jazz_ui.src.app.pages.data-service.data_service	14 core.jazz_ui.src.app.core.services.request_service	16 core.jazz_ui.src.app.secondary-components.filter-tags.filter-tags_component	17 core.jazz_ui.src.app.core.services.admin-utils_service	20 core.jazz_ui.src.app.pages.environment-deployment.env-deployments-section_component	22 core.jazz_ui.src.app.pages.environment-overview.env-overview-section_component	28 core.jazz_ui.src.app.pages.service-detail.service-detail_component	35 core.jazz_ui.src.app.secondary-components.table-template.table-template_component	39 core.jazz_ui.src.app.pages.services-list.services-list_component
1 com.slf.model
2 core.jazz_ui.src.app.SharedService_service
3 core.jazz_ui.src.app.adv-filter_directive
4 core.jazz_ui.src.app.advanced-filter_service
5 core.jazz_ui.src.app.core.helpers.cronparser_service
6 core.jazz_ui.src.app.core.services.authentication_service
7 core.jazz_ui.src.app.core.services.datacache_service
8 core.jazz_ui.src.app.core.services.message_service
9 core.jazz_ui.src.app.core.services.rename-field_service
10 core.jazz_ui.src.app.core.services.utils_service
11 core.jazz_ui.src.app.pages.data-service.data_service
12 com.slf.services	5
13 core.jazz_ui.src.app.app_component						1		1
14 core.jazz_ui.src.app.core.services.request_service						1				1
15 core.jazz_ui.src.app.pages.landing.landing_component						1	1
16 core.jazz_ui.src.app.secondary-components.filter-tags.filter-tags_component							1
17 core.jazz_ui.src.app.core.services.admin-utils_service												1
18 core.jazz_ui.src.app.pages.environment-assets.env-assets-section_component				1		1	1	1	1	1		1
19 core.jazz_ui.src.app.pages.environment-codequality.env-codequality-section_component								1	1	1		1
20 core.jazz_ui.src.app.pages.environment-deployment.env-deployments-section_component						1	1	1				1
21 core.jazz_ui.src.app.pages.environment-logs.env-logs-section_component			1	1		1	1	1				1	1
22 core.jazz_ui.src.app.pages.environment-overview.env-overview-section_component						1	1	1			1	1
23 core.jazz_ui.src.app.pages.error404.error404_component							1	1				1
24 core.jazz_ui.src.app.pages.jenkins-status.jenkins-status_component						1	1	1				1
25 core.jazz_ui.src.app.pages.login.oss.login_component						1		1				1
26 core.jazz_ui.src.app.pages.service-access-control.service-access-control_component								1				1
27 core.jazz_ui.src.app.pages.service-cost.service-cost_component			1	1		1	1	1				1	1
28 core.jazz_ui.src.app.pages.service-detail.service-detail_component		1				1	1	1				1
29 core.jazz_ui.src.app.pages.service-logs.service-logs_component			1	1		1	1	1				1	1
30 core.jazz_ui.src.app.pages.service-metrics.service-metrics_component								1	1	1		1
31 core.jazz_ui.src.app.pages.testapi.test-api_component							1					1
32 core.jazz_ui.src.app.secondary-components.env-try-service-sidebar.env-try-service-sidebar_component												1
33 core.jazz_ui.src.app.secondary-components.jazz-header.jazz-header_component						1		1				1
34 core.jazz_ui.src.app.secondary-components.service-overview-multienv.service-overview-multienv_component						1	1	1				1
35 core.jazz_ui.src.app.secondary-components.table-template.table-template_component						1	1					1
36 core.jazz_ui.src.app.pages.admin-dashboard.admin-dashboard_component												1		1
37 core.jazz_ui.src.app.pages.environment-detail.environment-detail_component							1	1			1	1			1	1
38 core.jazz_ui.src.app.pages.service-overview.service-overview_component					1	1	1	1				1					1
39 core.jazz_ui.src.app.pages.services-list.services-list_component		1				1	1	1				1						1
40 core.jazz_ui.src.app.secondary-components.create-service.oss.create-service_component					1	1	1	1				1							1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 50% · Weak · gated by R1, X5 ·

The Good

D3 · JavaScript God Classes 8.6 D4 · JavaScript Code Duplication 9.8 D17 · JavaScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.8 R10 · React / TS Code Duplication 7.3 R2 · React / TS Cyclomatic Complexity 8.0 R3 · React / TS Large Files 7.9 R7 · React / TS Dead Code 7.9 X1 · Repo Async correctness 7.1 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

D1 · JavaScript Cyclomatic Complexity 6.3 X3 · Repo Exception handling 5.3

The Ugly

D2 · JavaScript Cognitive Complexity 4.2 R1 · React / TS Type Safety 3.5 X23 · Repo Unguarded diagnostic materialisation 3.2 X29 · Repo Per-element action decided by a fixed element 3.5 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 65% · Adequate · gated by AX10 ·

The Good

D5 · JavaScript Coupling 10.0 D6 · JavaScript Cohesion (LCOM4) 9.5 D26 · JavaScript Project Cohesion 10.0 D35 · JavaScript Change Coupling 9.8 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX8 · Repo Test isolation 10.0 R11 · React / TS Import Boundaries 8.2 R9 · React / TS Circular Imports 10.0

The Ugly

D22 · JavaScript Internal API Consistency 2.0 AX10 · Repo Code composition 0.0

At a glance — Maturity · 63% · Adequate · gated by D34 ·

The Good

D15 · JavaScript Churn × Complexity Hotspots 10.0 D21 · JavaScript Naming Consistency 10.0 M1 · Repo Documentation (README) 9.3 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 10.0

The Bad

D19 · JavaScript Documentation Quality 6.0 M2 · Repo Architecture documentation 5.0

The Ugly

D34 · JavaScript Knowledge Freshness 0.0

At a glance — Readiness · 45% · Weak · gated by D9, D13, R8 ·

The Good

D11 · JavaScript Test Reliability 10.0 D14 · JavaScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 7.7

The Bad

D10 · JavaScript Test Quality 5.8 R6 · React / TS Tooling 6.7

The Ugly

D9 · JavaScript Test Distribution 3.6 D13 · JavaScript Secret Scanning 0.0 P3 · Repo Security & performance tooling 4.0 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 59% · Adequate · gated by D28, D29, D30, D43 ·

The Good

D31 · JavaScript IaC & Container Security 10.0 D32 · JavaScript Data Compliance (PII/GDPR) 8.1 D44 · JavaScript Platform End-of-Life 10.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0

The Ugly

D28 · JavaScript Secrets (history) 0.0 D29 · JavaScript Static Analysis (SAST) 2.1 D30 · JavaScript Dependency Vulnerabilities 0.0 D43 · JavaScript Malicious Dependencies 0.0 X24 · Repo Document value interpolated into markup unescaped 2.7

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.0

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 category	Findings	Severity
A03:2025 — Software Supply Chain Failures	54	High / Critical
A05:2025 — Injection	32	High / Critical
A07:2025 — Authentication Failures	17	High / Critical
A01:2025 — Broken Access Control	2	Medium
A08:2025 — Software or Data Integrity Failures	1	Medium

Roadmap

Immediately resolve the three leaked secrets in the login and sidebar components to secure the application. Enhance test reliability by improving distribution across tiers and fixing forty tests that lack assertions, followed by two tests with commented-out assertions. Finally, clean up the dependency tree by removing unused packages and explicitly declaring imports to reduce maintenance overhead.

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

Do this	Helps	Effort	Dimension
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED.	+5.7 pts	Low	Secret Scanning
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with websiteservices.e2e-spec.ts (2).	+2.7 pts	Low	Test Quality
Improve Test Distribution — currently 3.6/10.	+5.0 pts	Medium	Test Distribution
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+4.8 pts	Medium	Dependency Hygiene
Resolve the 40 No assertions finding(s) in Test Quality — start with lambdaservices.e2e-spec.ts (7), apiservices.e2e-spec.ts (6), slsappservices.e2e-spec.ts (6).	+4.3 pts	Medium	Test Quality
Enable Dependabot/Renovate or a dependency-review gate.	+2.6 pts	Medium	Security & performance tooling
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 `?`).	+2.6 pts	Medium	Nullable reference types
Migrate the remaining .js/.jsx files to TypeScript.	+1.8 pts	Medium	Type Safety

File quality

Per-file score 0–10 — a quality signature. Of 125 files carrying findings, judged against the Production bar: 3% slop · 71% mixed · 26% near-clean.

File	Score	Band	Worst signal
REDACTED	0.2	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	1.1	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.6	Slop	Secret Scanning: Leaked secret: REDACTED
REDACTED	3.7	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	4.0	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	4.0	Mixed	Static Analysis (SAST): Medium: REDACTED
core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts	4.1	Mixed	Test Quality: Assertions commented out: Verify METRICS COUNT for Website
REDACTED	4.6	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	4.9	Mixed	Static Analysis (SAST): Medium: REDACTED
core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts	4.9	Mixed	Cognitive Complexity: EnvLogsSectionComponent.setAssetName (cognitive 17)
REDACTED	5.1	Mixed	Dependency Vulnerabilities: Critical CVE: REDACTED
core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts	5.5	Mixed	Cyclomatic Complexity: ServiceMetricsComponent.applyFilter (cyclomatic 33)
core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts	5.6	Mixed	Cognitive Complexity: EnvOverviewSectionComponent.onRoleNameChange (cognitive 20)
REDACTED	5.7	Mixed	Data Compliance (PII/GDPR): Medium: REDACTED
REDACTED	5.8	Mixed	Secrets (history): High secret: REDACTED
REDACTED	6.1	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.4	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.9	Mixed	Static Analysis (SAST): Medium: REDACTED
core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts	7.0	Mixed	Cyclomatic Complexity: ServiceOverviewComponent.check_empty_fields (cyclomatic 28)
core/jazz_ui/e2e/05-lambdaservices/lambdaservices.e2e-spec.ts	7.0	Mixed	Test Quality: No assertions: Verify Lambda Deployments

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

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

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

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 12

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

Watchdog 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. 71 of 75 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 75 dimensions across the health lenses

D1D2D3D4D5D6D9D10D11D13D14D15D17D19D21D22D26D28D29D30D31D32D34D35D43D44AX10AX3AX5AX8GD1IC1M1M2M3M4P1P10P3P4P6PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X20X21X22X23X24X25X26X27X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 849 of 863 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a1634a-9db5-7611-9795-49fe0abb44a4.

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.

D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 mocha suite in core/jazz_acl/ was NOT MEASURED: the mocha run in core/jazz_acl/ produced no per-test report (Error: Cannot find module 'mongodb'). 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 — Watchdog measured this, but not all of it. What it 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 mocha suite in core/jazz_assets/ was NOT MEASURED: the mocha run in core/jazz_assets/ produced no per-test report (TypeError: require(...) is not a function). 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 — Watchdog measured this, but not all of it. What it 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 mocha suite in core/jazz_cloud-logs-streamer/ was NOT MEASURED: the mocha run in core/jazz_cloud-logs-streamer/ produced no per-test report (TypeError: logger.setLevel is not a function). 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 — Watchdog measured this, but not all of it. What it 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 mocha suite in core/jazz_delete-serverless-service/ was NOT MEASURED: the mocha run in core/jazz_delete-serverless-service/ produced no per-test report (> delete-serverless-service@0.0.1 test). 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 — Watchdog measured this, but not all of it. What it 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 mocha suite in core/jazz_deployments/ was NOT MEASURED: the mocha run in core/jazz_deployments/ produced no per-test report (TypeError: require(...) is not a function). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 13 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
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. All 159 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 1 of the 540 production source files in this repository: 381 are under the ~2,400-byte size floor this dimension measures over, and the remaining 158 have no attributable history left to measure.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .js (35,096 lines, 58% of production source), .ts (17,549 lines, 29% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 13 task marker(s) (TODO/FIXME/HACK/XXX) across 5 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D39 IL Efficiency — not measured this run — Watchdog 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 authorization 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 authorization controls.
C3 Audit Trail — not measured this run — Watchdog 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 audit 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 audit controls.
C4 Data Retention — not measured this run — Watchdog 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 retention 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 retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog 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 data-subject rights 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 data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 256 further occurrence(s) are not listed individually; the score already reflects all 296.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 58 further occurrence(s) are not listed individually; the score already reflects all 98.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 16 further occurrence(s) are not listed individually; the score already reflects all 56.
X23 Unguarded diagnostic materialisation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 120 further occurrence(s) are not listed individually; the score already reflects all 160.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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 requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity6.3 / 10Adequate✓ 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 6.3 / 10 · rule-coverage 100% · ceiling Prevented

85 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was handler at 72. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being utils.sortUtil at 20 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: core/jazz_deployments/components/utils.js (utils.sortUtil at 20), core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts (ServiceCostComponent.fetchServices at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

index.handler (cyclomatic 41) · ×2REDACTED:29

(anonymous)::DatePickerOptions (cyclomatic 23) · ×2core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:16

exports::getServiceData (cyclomatic 23) · ×2core/jazz_create-serverless-service/components/crud/create.js:40

bootstrap.Tooltip.show (cyclomatic 22) · ×2core/jazz-web/js/bootstrap.js:1437

handler (cyclomatic 22) · ×2core/jazz_assets/index.js:33

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

What to do

Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with handler (cyclomatic 72), index.handler (cyclomatic 61). — 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 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity4.2 / 10Weak✓ 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 4.2 / 10 · rule-coverage 100% · ceiling Prevented

156 method(s) exceeded the cognitive complexity threshold of 15; the worst was index.getServiceData at 106.

exports::getServiceData (cognitive 26) · ×3core/jazz_create-serverless-service/components/crud/create.js:40

(anonymous)::generateCalendar (cognitive 45) · ×2core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:158

sortUtil (cognitive 33) · ×2core/jazz_services/components/utils.js:209

bootstrap.Tooltip.show (cognitive 25) · ×2core/jazz-web/js/bootstrap.js:1437

index.genericInputValidation (cognitive 25) · ×2core/jazz_environments/index.js:170

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

What to do

Bring the 11 bodies over 60 down to 60 or less in Cognitive Complexity — start with index.getServiceData (cognitive 106), getServiceData (cognitive 106), handler (cognitive 106). — 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 11 together lifts Cognitive Complexity from 4.2 to about 5.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes8.6 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

31 god class(es) detected.

FileTooLong: js/bootstrap.js · ×10core/jazz-web/js/bootstrap.js

TooManyMethods: ServiceOverviewComponent · ×7core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:23

ClassTooLong: CreateServiceComponent · ×7REDACTED:26

FunctionTooLong: index.handler · ×4core/jazz_t-vault/index.js:37

MethodTooLong: ServiceMetricsComponent.applyFilter · ×3core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:416

What to do

Resolve the 10 FileTooLong finding(s) in God Classes — start with bootstrap.js (2), service-overview.component.ts, REDACTED. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 7 TooManyMethods finding(s) in God Classes — start with service-overview.component.ts, REDACTED, env-overview-section.component.ts. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 ClassTooLong finding(s) in God Classes — start with REDACTED, REDACTED, env-overview-section.component.ts. — One of this dimension's main actionable groups (7 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.8 / 10Stronggated by 22 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

22 duplicated block group(s) detected. Measured on part of this repository only: .js, .ts (87% 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 (17 lines × 3) · ×3templates/api-template-python/components/logger.py:93

Duplicated block (10 lines × 2) · ×2templates/api-template-java/src/main/java/com/slf/util/ErrorUtil.java:20

Duplicated block (9–10 lines × 2)templates/sls-app-template-java/src/main/java/com/slf/services/functions/function1/Function1.java:62

Duplicated block (19 lines × 2)templates/api-template-java/src/main/java/com/slf/exceptions/BaseException.java:12

Duplicated block (27 lines × 3)templates/api-template-java/src/main/java/com/slf/model/ErrorInfo.java:10

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

What to do

Resolve the 3 Duplicated block (17 lines × 3) finding(s) in Code Duplication — start with logger.go (2), logger.py. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ErrorUtil.java, JsonUtil.java. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Duplicated block (9–10 lines × 2) finding(s) in Code Duplication — start with Function1.java. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

51 production modules (Maven+npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 9 of the 51 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.5 / 10Stronggated by 3 serious findings✓ 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 9.5 / 10 · rule-coverage 100% · ceiling Verified

3 of 70 classes have LCOM4 above 3.

Low cohesion: TableTemplateComponent (LCOM4 5) · ×3core/jazz_ui/src/app/secondary-components/table-template/table-template.component.ts:10

What to do

Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with table-template.component.ts, jazz-header.component.ts, env-overview-section.component.ts. — One of this dimension's main actionable groups (3 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution3.6 / 10Weak✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

169 test methods: 86 unit, 0 integration, 0 BDD, 83 e2e. The JavaScript/TypeScript suite contributes 157 `it`/`test` case(s) across 58 test file(s) declaring at least one beside 4 .NET test method(s); its tier split is read from package names and paths only. The Python suite contributes 4 test function(s) across 4 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Go suite contributes 4 test case(s) across 4 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.

What to do

Improve Test Distribution — currently 3.6/10. — 169 test methods: 86 unit, 0 integration, 0 BDD, 83 e2e. The JavaScript/TypeScript suite contributes 157 `it`/`test` case(s) across 58 test file(s) declaring at least one beside 4 .NET test method(s); its tier split is read from package names and paths only. The Python suite contributes 4 test function(s) across 4 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Go suite contributes 4 test case(s) across 4 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality5.8 / 10Adequate✓ 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 5.8 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 42 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 157 tests.

Assertions commented out: Verify METRICS COUNT for Website · ×2core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts:177

No assertions: backtologin · ×40core/jazz_ui/e2e/01-register/register.e2e-spec.ts:34

Test project verifies nothing: templates/react-website-template/apptemplates/react-website-template/app/src/App.test.js:5

What to do

Resolve the 40 No assertions finding(s) in Test Quality — start with lambdaservices.e2e-spec.ts (7), apiservices.e2e-spec.ts (6), slsappservices.e2e-spec.ts (6). — One of this dimension's main actionable groups (40 warning-level).
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with websiteservices.e2e-spec.ts (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with App.test.js. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_acl/; mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_admin/ (36 tests); mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_apigee-proxy-aws/ (6 tests); mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_asset-event-handler/ (32 tests); mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_assets/; mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_cloud-logs-streamer/; mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_codeq/ (41 tests); mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_cognito-admin-authorizer/ (1 tests); mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_cognito-authorizer/ (9 tests); mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_create-serverless-service/ (48 tests); mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_delete-serverless-service/; mocha via `npm install --ignore-scripts` (no lockfile) in core/jazz_deployments/): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

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 0.0 / 10 · rule-coverage 100% · ceiling Prevented

2 secret(s) detected.

REDACTED

What to do

Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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 55 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 2 direct `PackageReference`(s), and 54 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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

0 deducted debt markers + 0 dead symbols across 0 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .js, .ts (87% of production source) was not read, and carries at least 13 uncounted task marker(s) in 5 file(s).

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

Do you agree with this assessment?

D19 · Documentation QualityAdequate◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The root Jazz serverless platform README is clear and well-structured: a strong branding banner with build status, contributors badge, license, release, Gitter, Slack, and an overview section that states what the project does (serverless development platform) plus three bullet points about services, deployment targets, and CI/CD. It also has a full outline of user guide sections including architecture docs, installation, usage examples, contribution guidance, and licence. The directory READMEs for builds/*, core/jazz_acl/, core/jazz_cognito-authorizer/, etc., each document their own subdirectory (configuration files, service metadata loader, Jenkins build packs) without referencing the root overview or providing install/usage guidance for those tiers.

What to do

Improve Documentation Quality — currently 6.0/10. — The root Jazz serverless platform README is clear and well-structured: a strong branding banner with build status, contributors badge, license, release, Gitter, Slack, and an overview section that states what the project does (serverless development platform) plus three bullet points about services, deployment targets, and CI/CD. It also has a full outline of user guide sections including architecture docs, installation, usage examples, contribution guidance, and licence. The directory READMEs for builds/*, core/jazz_acl/, core/jazz_cognito-authorizer/, etc., each document their own subdirectory (configuration files, service metadata loader, Jenkins build packs) without referencing the root overview or providing install/usage guidance for those tiers.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D22 · Internal API ConsistencyCritical◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

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

1 API inconsistencies across 3 exposed types.

Redundant type definition: SlimScrollOptions is a concrete class that duplicates all properties of the interface ISlimScrollOptions and accepts it in its constructor. This creates unnecessary coupling and maintenance overhead without adding distinct behavior or value.

What to do

Resolve the 1 Redundant type definition finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D26 · Project Cohesion10.0 / 10Exemplary✓ 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, LLM-independent.

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

0 of 1 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

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 0.0 / 10 · rule-coverage 100% · ceiling Documented

13 finding(s): 0 critical, 13 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED

What to do

Resolve the 13 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (13 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)2.1 / 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 2.1 / 10 · rule-coverage 100% · ceiling Documented

32 finding(s): 0 critical, 5 high, 27 medium, 0 low. 4 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 7 file(s) — `core/jazz_slack-event-handler/event.json`, `core/jazz_test-lambda/config/dev-config.json`, `core/jazz_test-lambda/config/prod-config.json`, `core/jazz_test-lambda/config/stg-config.json`, `core/jazz_ui/src/config/config.dev.json`, … (+2 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED

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

What to do

Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).

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

Do you agree with this assessment?

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.

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

54 finding(s): 15 critical, 25 high, 14 medium, 0 low.

REDACTED

What to do

Resolve the 24 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (20), REDACTED (4). — One of this dimension's main actionable groups (24 issue-level).
Resolve the 14 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13), REDACTED. — One of this dimension's main actionable groups (14 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

Do you agree with this assessment?

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

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

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

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

Do you agree with this assessment?

D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

2 finding(s): 0 critical, 0 high, 2 medium, 0 low.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D34 · Knowledge Freshness0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

159 of 159 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts. Counted over 159 of the 540 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×156core/jazz_metrics/index.js:1

Most significant orphaned file · ×3core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1

Dormant codebase

What to do

Resolve the 156 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (36), REDACTED (12), getList.js (6). — One of this dimension's main actionable groups (156 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with service-overview.component.ts, REDACTED, service-metrics.component.ts. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling9.8 / 10Stronggated by 4 serious findings✓ 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 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: service-metrics.component.ts↔filter-modal.component.ts 94%; env-logs-section.component.ts↔REDACTED 74%; REDACTED↔advanced-filters.component.ts 71%

Change coupling: env-logs-section.component.ts ↔ REDACTED · ×3core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:1

Change-coupling hub: service-metrics.component.ts → env-logs-section.component.ts, advanced-filters.component.ts, filter-modal.component.ts, metrics-carousel.component.tscore/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts

What to do

Resolve the 3 Change coupling finding(s) in Change Coupling — start with env-logs-section.component.ts (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with service-metrics.component.ts. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D43 · Malicious Dependencies0.0 / 10Critical✓ 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. Scored 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. SCORED, not informational.

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

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

REDACTED

What to do

Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

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 5 platform declaration(s) and 14 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition0.0 / 10Critical✓ 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.

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

Do you agree with this assessment?

IC1 · Incompleteness & stubs7.8 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

`instantiate` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — builds/jazz_azure-create-service/components/CommandMapping.js:18
The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. (×4) — core/jazz_services/components/utils.js:180, core/jazz_ui/src/app/core/services/request.service.ts:113, core/jazz_ui/src/app/core/services/request.service.ts:154, …
`errorIncluded` has an empty body — confirm it's an intentional no-op and not an unfinished method. — core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.ts:268
`ngOnInit` has an empty body — confirm it's an intentional no-op and not an unfinished method. — core/jazz_ui/src/app/secondary-components/create-service/focus.directive.ts:13

What to do

Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.

Do you agree with this assessment?

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

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ 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.

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

What to do

Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

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.

Do you agree with this assessment?

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

Do you agree with this assessment?

P3 · Security & performance tooling4.0 / 10Weak✓ 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.

What to do

Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

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

Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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 the language 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.readFileSync` in `createOrUpdateApiGatewayWithSwaggerJson` 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:224
`fs.readFileSync` in `uploadFilesToStorageFromZipBase64` 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:362
`fs.readFileSync` in `exports` 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. — builds/jazz_azure-create-service/index.js:9

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.

Do you agree with this assessment?

R1 · Type Safety3.5 / 10Weak✓ 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.

203 typed · 379 plain JS — the untyped files are builds/azure-config-pack/nodejs/index.js, builds/jazz-build-module/apigee/templates/coreAPI_default/Common/resources/jsc/cf_CORS.js, builds/jazz-build-module/apigee/templates/coreAPI_secure/Common/resources/jsc/cf_CORS.js, builds/jazz_azure-create-service/components/ApiApp.js, builds/jazz_azure-create-service/components/ClientFactory.js, builds/jazz_azure-create-service/components/CommandMapping.js (+373 more).

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication7.3 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.

core/jazz-web/ and templates/static-website-template/app/ are near-verbatim copies of each other: 10 files are byte-identical under the same relative paths (~10068 lines; the trees hold 12 and 11 files). That is one structural fact, not 10 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. — core/jazz-web/css/bootstrap.css:1
builds/jazz-build-module/apigee/templates/coreAPI_default/ and builds/jazz-build-module/apigee/templates/coreAPI_secure/ are near-verbatim copies of each other: 45 files are byte-identical under the same relative paths (~517 lines; the trees hold 47 and 47 files). That is one structural fact, not 45 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — builds/jazz-build-module/apigee/templates/coreAPI_default/Proxy/proxies/ProxyEndpoint.xml.ftl:1
130 duplicated blocks under core/ have copies in at least two of the sibling directories jazz_acl, jazz_admin, jazz_apigee-proxy-aws, jazz_asset-event-handler, jazz_assets, jazz_cloud-logs-streamer (+29 more sibling(s) not listed) — 99 of them are reported below, and 31 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 130 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 130 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 130 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. — core/jazz_deployments/index.js:37
41 duplicated blocks under core/jazz_ui/src/app/pages/ have copies in at least two of the sibling directories environment-assets, environment-codequality, environment-deployment, environment-detail, environment-logs, environment-overview (+7 more sibling(s) not listed) — 33 of them are reported below, and 8 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 41 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 41 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 41 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. — core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:365
25 duplicated blocks under core/jazz_ui/src/app/ have copies in at least two of the sibling directories pages, primary-components, secondary-components — 21 of them are reported below, and 4 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 25 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 25 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 25 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. — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:882
6 of the duplicated blocks reported below have copies in at least two of the sibling directories core, templates under the repository root. That concentration is one structural fact, not 6 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 6 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. — core/jazz_acl/components/logger.js:16
core/jazz_deployments/index.js:37 · core/jazz_environments/index.js:34 — the two spans are one implementation copied and then locally edited — 626 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. — core/jazz_deployments/index.js:37
REDACTED:29 · core/jazz_token-authorizer/index.js:29 — the two spans are one implementation copied and then locally edited — 786 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. — REDACTED:29
core/jazz_cognito-authorizer/components/auth-policy.js:37 · core/jazz_token-authorizer/index.js:200 — 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. — core/jazz_cognito-authorizer/components/auth-policy.js:37
core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:882 · core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts:252 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:882
core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:365 · core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:502 — 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. — core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:365
core/jazz_environments/components/utils.js:51 · core/jazz_services/components/utils.js:47 — the two spans are one implementation copied and then locally edited — 625 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. — core/jazz_environments/components/utils.js:51
core/jazz_environments/components/validation/common.js:69 · core/jazz_services/components/validation/common.js:170 — the two spans are one implementation copied and then locally edited — 488 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. — core/jazz_environments/components/validation/common.js:69
core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts:90 · core/jazz_ui/src/app/secondary-components/advanced-filters/internal/advanced-filters.component.ts:67 — the two spans are one implementation copied and then locally edited — 597 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. — core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts:90
core/jazz_create-serverless-service/components/validate-sls-yml.js:17 · core/jazz_environments/components/validate-sls-yml.js:17 — these 2 files are line-for-line copies of one another — 93 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. — core/jazz_create-serverless-service/components/validate-sls-yml.js:17
core/jazz_ui/src/app/secondary-components/filter-metrics/filter-metrics.component.ts:23 · core/jazz_ui/src/app/secondary-components/filter-modal/filter-modal.component.ts:74 — the two spans are one implementation copied and then locally edited — 519 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. — core/jazz_ui/src/app/secondary-components/filter-metrics/filter-metrics.component.ts:23
core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:631 · core/jazz_ui/src/app/secondary-components/table-template/table-template.component.ts:184 — the two spans are one implementation copied and then locally edited — 488 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. — core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:631
core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1026 · core/jazz_ui/src/app/secondary-components/table-template/table-template.component.ts:184 — the two spans are one implementation copied and then locally edited — 488 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. — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1026
core/jazz_asset-event-handler/index.js:73 · core/jazz_environment-event-handler/index.js:75 — 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. — core/jazz_asset-event-handler/index.js:73
REDACTED:368 · REDACTED:241 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:368
core/jazz_deployments-event-handler/index.js:40 · core/jazz_environment-event-handler/index.js:38 — the two spans are one implementation copied and then locally edited — 533 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. — core/jazz_deployments-event-handler/index.js:40
core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:236 · REDACTED:287 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:236
core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:288 · REDACTED:1238 — the two spans are one implementation copied and then locally edited — 398 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. — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:288
core/jazz_ui/src/app/primary-components/checkbox-group-region/checkbox-group-region.component.ts:7 · core/jazz_ui/src/app/primary-components/checkbox-group/checkbox-group.component.ts:7 — 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. — core/jazz_ui/src/app/primary-components/checkbox-group-region/checkbox-group-region.component.ts:7
core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:680 · core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1379 — the two spans are one implementation copied and then locally edited — 336 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. — core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:680
core/jazz_acl/components/logger.js:16 · core/jazz_admin/components/logger.js:16 · core/jazz_apigee-proxy-aws/components/logger.js:16 · core/jazz_asset-event-handler/components/logger.js:16 · +35 more site(s) not listed — the 39 copies are spread across 39 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. There is one copy in each of 39 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — core/jazz_acl/components/logger.js:16
core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.ts:271 · core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:430 — 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. — core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.ts:271
core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:458 · REDACTED:660 — 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. — core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:458
REDACTED:33 · REDACTED:33 — 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:33
core/jazz_asset-event-handler/index.js:339 · core/jazz_environment-event-handler/index.js:606 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/jazz_asset-event-handler/index.js:339
core/jazz_acl/components/scm/bitbucket.js:72 · core/jazz_acl/components/scm/gitlab.js:131 — the two spans are one implementation copied and then locally edited — 285 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. — core/jazz_acl/components/scm/bitbucket.js:72
core/jazz_email/components/error-handler.js:24 · core/jazz_is-service-available/components/error-handler.js:24 · core/jazz_login/components/error-handler.js:24 · core/jazz_token-authorizer/components/error-handler.js:25 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/jazz_email/components/error-handler.js:24
core/jazz_environment-event-handler/components/error-handler.js:17 · core/jazz_events-handler/components/error-handler.js:8 · core/jazz_services-handler/components/error-handler.js:24 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/jazz_environment-event-handler/components/error-handler.js:17
core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:539 · core/jazz_ui/src/app/pages/services-list/services-list.component.ts:266 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:539
core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts:19 · core/jazz_ui/src/app/secondary-components/advanced-filters/internal/advanced-filters.component.ts:15 — the two spans are one implementation copied and then locally edited — 355 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. — core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts:19
core/jazz_ui/src/app/pages/services-list/services-list.component.ts:338 · core/jazz_ui/src/app/pages/services-list/services-list.component.ts:483 — the two spans are one implementation copied and then locally edited — 269 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. — core/jazz_ui/src/app/pages/services-list/services-list.component.ts:338
core/jazz_admin/components/error-handler.js:9 · core/jazz_delete-serverless-service/components/error-handler.js:25 · core/jazz_environments/components/error-handler.js:25 · core/jazz_logout/components/error-handler.js:25 · +3 more site(s) not listed — the 7 copies are spread across 7 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/jazz_admin/components/error-handler.js:9
core/jazz_asset-event-handler/components/error-handler.js:17 · core/jazz_deployments-event-handler/components/error-handler.js:8 · core/jazz_slack-event-handler/components/error-handler.js:25 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/jazz_asset-event-handler/components/error-handler.js:17
core/jazz_asset-event-handler/index.js:209 · core/jazz_asset-event-handler/index.js:255 — all 2 copies are in the same file, 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. — core/jazz_asset-event-handler/index.js:209
core/jazz_asset-event-handler/utils/utils.js:20 · core/jazz_environment-event-handler/utils/utils.js:20 — 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. — core/jazz_asset-event-handler/utils/utils.js:20

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.

Do you agree with this assessment?

R11 · Import Boundaries8.2 / 10Strong✓ 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.

core/jazz_ui/src/app/environment-module/environment.module.ts:12 reaches into another package with a relative path (../primary-components/daterange-picker/ng2-datepicker) — import the package by name instead. — core/jazz_ui/src/app/environment-module/environment.module.ts:12
core/jazz_ui/src/app/primary-components/daterange-picker/daterange-picker.component.ts:2 reaches into another package with a relative path (./ng2-datepicker) — import the package by name instead. — core/jazz_ui/src/app/primary-components/daterange-picker/daterange-picker.component.ts:2
core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.d.ts:3 reaches into another package with a relative path (../../ng2-slimscroll) — import the package by name instead. — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.d.ts:3
core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.module.js:4 reaches into another package with a relative path (../../ng2-slimscroll) — import the package by name instead. — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.module.js:4
core/jazz_ui/src/app/service-module/service.module.imports.common.ts:5 reaches into another package with a relative path (../primary-components/daterange-picker/ng2-datepicker) — import the package by name instead. — core/jazz_ui/src/app/service-module/service.module.imports.common.ts:5
core/jazz_ui/src/app/service-module/service.module.ts:21 reaches into another package with a relative path (../primary-components/daterange-picker/ng2-datepicker) — import the package by name instead. — core/jazz_ui/src/app/service-module/service.module.ts:21
core/jazz_ui/src/app/shared-module/shared.module.ts:36 reaches into another package with a relative path (../primary-components/daterange-picker/ng2-datepicker) — import the package by name instead. — core/jazz_ui/src/app/shared-module/shared.module.ts:36
core/jazz_ui/src/polyfills.ts:19 imports zone.js/dist/zone, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — core/jazz_ui/src/polyfills.ts:19
templates/angular-website-template/app/src/polyfills.ts:58 imports zone.js/dist/zone, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/angular-website-template/app/src/polyfills.ts:58

What to do

Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.

Do you agree with this assessment?

R2 · Cyclomatic Complexity8.0 / 10Strong✓ 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.

(anonymous) has cyclomatic complexity 49 and cognitive complexity 106; 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. — core/jazz_create-serverless-service/index.js:317
handler has cyclomatic complexity 49 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. — core/jazz_t-vault/index.js:37
handler has cyclomatic complexity 47 and cognitive complexity 73; 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. — core/jazz_create-serverless-service/index.js:38
createService has cyclomatic complexity 38 and cognitive complexity 57; 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:667
getNotificationMessage 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. — core/jazz_slack-event-handler/components/utils.js:19
applyFilter has cyclomatic complexity 32 and cognitive complexity 38; 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. — core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:416
disableForm has cyclomatic complexity 32 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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:977
(anonymous) has cyclomatic complexity 29 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. — core/jazz_environments/index.js:171
check_empty_fields has cyclomatic complexity 28 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:758
handler has cyclomatic complexity 26 and cognitive complexity 48; 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. — core/jazz_logs/index.js:34
processACLRequest has cyclomatic complexity 25 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/jazz_acl/index.js:55
handler has cyclomatic complexity 25 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/jazz_usermanagement/index.js:36
(anonymous) has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/jazz_scm-webhook/index.js:131
handler has cyclomatic complexity 24 and cognitive complexity 26; 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. — core/jazz_services/index.js:34
getServiceData has cyclomatic complexity 23 and cognitive complexity 26; 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. — core/jazz_create-serverless-service/components/crud/create.js:40
DatePickerOptions has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:16
SlimScrollOptions has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/classes/slimscroll-options.class.js:2
constructor has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/classes/slimscroll-options.class.ts:28
generateCalendar has cyclomatic complexity 22 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. — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:158
(anonymous) has cyclomatic complexity 22 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/jazz_environments/index.js:47

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files7.9 / 10Strong✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts has 1376 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1
REDACTED has 1172 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
REDACTED has 824 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
core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts has 796 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:1
core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts has 774 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:1
core/jazz_metrics/index.js has 730 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_metrics/index.js:1
core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts has 717 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:1
core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts has 710 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:1
core/jazz_ui/src/app/pages/services-list/services-list.component.ts has 676 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/services-list/services-list.component.ts:1
core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts has 599 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:1
core/jazz_environment-event-handler/index.js has 595 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_environment-event-handler/index.js:1
core/jazz_t-vault/components/utils/vault.js has 555 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_t-vault/components/utils/vault.js:1
core/jazz_deployments/index.js has 552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_deployments/index.js:1
core/jazz_create-serverless-service/index.js has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_create-serverless-service/index.js:1
core/jazz_slack-channel/index.js has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_slack-channel/index.js:1
REDACTED has 502 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
REDACTED has 459 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
core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts:1
REDACTED has 453 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
core/jazz_token-authorizer/index.js has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_token-authorizer/index.js:1
core/jazz_usermanagement/index.js has 437 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_usermanagement/index.js:1
REDACTED has 424 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
core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts has 414 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts:1
core/jazz_metrics/components/utils.js has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_metrics/components/utils.js:1
core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts:1

What to do

Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.

Do you agree with this assessment?

R4 · Test Coverage7.7 / 10Strong✓ 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) — REDACTED:1, core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:1, REDACTED:1, …

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R6 · Tooling6.7 / 10Adequate✓ 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.

test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

Add `tsc --noEmit` as package.json scripts and run them in CI.

Do you agree with this assessment?

R7 · Dead Code7.9 / 10Strong✓ 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.

8 file(s) (~340 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — templates/sls-app-template-nodejs
Unreachable from the 53 application, 26 tooling and 114 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 (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (core/jazz_ui/src/app/service-module/service.module.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — REDACTED, core/jazz_ui/src/app/service-module/service.route.ts
no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×10) — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/directives/slimscroll.directive.js, core/jazz_ui/src/app/pages/service-metrics/data.ts, core/jazz_ui/src/app/service-module/service.module.ts, …
no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (core/jazz_ui/src/app/admin-module/admin.module.ts, core/jazz_ui/src/app/admin-module/admin.route.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — core/jazz_ui/src/app/pages/admin-dashboard/admin-dashboard.component.ts, core/jazz_ui/src/app/pages/admin/admin.component.ts
no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (core/jazz_ui/src/app/admin-module/admin.module.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — core/jazz_ui/src/app/primary-components/json-viewer/json-viewer.component.ts, core/jazz_ui/src/app/admin-module/admin.route.ts
no import path from any entry point (53 application, 26 tooling, 114 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 (×17) — core/jazz_asset-event-handler/utils/utils.js, core/jazz_environment-event-handler/utils/utils.js, core/jazz_events-handler/components/error-handler.js, …
no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (core/jazz_ui/src/app/admin-module/admin.module.ts, core/jazz_ui/src/app/pages/admin-dashboard/admin-dashboard.component.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — core/jazz_ui/src/app/core/services/admin-utils.service.ts
no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (REDACTED, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — core/jazz_ui/src/config/templates/java-yaml.ts, core/jazz_ui/src/config/templates/go-yaml.ts, core/jazz_ui/src/config/templates/nodejs-yaml.ts, …

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene0.0 / 10Critical✓ 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. (×13) — core/jazz_admin/components/utils.js:26, core/jazz_metrics/components/utils.js:28, core/jazz_metrics/components/utils.js:29, …
Declared in builds/jazz_azure-create-service/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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. 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://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.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. 2 such include(s) across the repository's markup. — core/jazz_ui/src/index.html:9

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.

Do you agree with this assessment?

X1 · Async correctness7.1 / 10Strong✓ Tool-verified

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.

`forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. (×2) — REDACTED:185, REDACTED:212
The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. (×2) — core/jazz_metrics/index.js:646, core/jazz_metrics/index.js:696

What to do

`async` callback passed to `forEach`

Do you agree with this assessment?

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.

Do you agree with this assessment?

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation3.2 / 10Weak✓ Tool-verified

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

`debug` at line 94 is called with an argument built by `JSON.stringify(result)` (line 94), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/casbin.js:94
`debug` at line 111 is called with an argument built by `JSON.stringify(action)` (line 111), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/casbin.js:111
`debug` at line 168 is called with an argument built by `JSON.stringify(payload)` (line 168), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/scm/gitlab.js:168
`debug` at line 170 is called with an argument built by `JSON.stringify(response)` (line 170), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/scm/gitlab.js:170
`debug` at line 109 is called with an argument built by `JSON.stringify(response)` (line 109), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/scm/bitbucket.js:109
`debug` at line 48 is called with an argument built by `JSON.stringify(payload)` (line 48), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:48
`debug` at line 52 is called with an argument built by `JSON.stringify(response)` (line 52), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:52
`debug` at line 95 is called with an argument built by `JSON.stringify(result)` (line 95), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:95
`debug` at line 122 is called with an argument built by `JSON.stringify(payload)` (line 122), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:122
`debug` at line 125 is called with an argument built by `JSON.stringify(response)` (line 125), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:125
`debug` at line 154 is called with an argument built by `JSON.stringify(payload)` (line 154), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:154
`debug` at line 157 is called with an argument built by `JSON.stringify(response)` (line 157), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:157
`debug` at line 194 is called with an argument built by `JSON.stringify(result)` (line 194), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:194
`debug` at line 222 is called with an argument built by `JSON.stringify(result)` (line 222), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:222
`debug` at line 258 is called with an argument built by `JSON.stringify(result)` (line 258), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/vault.js:258
`debug` at line 25 is called with an argument built by `JSON.stringify(dataDb)` (line 25), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/getList.js:25
`debug` at line 50 is called with an argument built by `JSON.stringify(scanResult)` (line 50), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/getList.js:50
`debug` at line 79 is called with an argument built by `JSON.stringify(scanparams)` (line 79), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/getList.js:79
`debug` at line 33 is called with an argument built by `JSON.stringify(payload)` (line 33), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/environment.js:33
`debug` at line 36 is called with an argument built by `JSON.stringify(response)` (line 36), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_acl/components/utils/environment.js:36
`verbose` at line 43 is called with an argument built by `JSON.stringify(payload)` (line 43), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_apigee-proxy-aws/index.js:43
`verbose` at line 59 is called with an argument built by `JSON.stringify(responseObj)` (line 59), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_apigee-proxy-aws/index.js:59
`debug` at line 195 is called with an argument built by `JSON.stringify(svcContext)` (line 195), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:195
`debug` at line 216 is called with an argument built by `JSON.stringify(assetApiPayload)` (line 216), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:216
`debug` at line 228 is called with an argument built by `JSON.stringify(svcPayload)` (line 228), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:228
`debug` at line 231 is called with an argument built by `JSON.stringify(body)` (line 231), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:231
`debug` at line 247 is called with an argument built by `JSON.stringify(svcContext)` (line 247), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:247
`debug` at line 262 is called with an argument built by `JSON.stringify(assetApiPayload)` (line 262), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:262
`debug` at line 274 is called with an argument built by `JSON.stringify(svcPayload)` (line 274), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:274
`debug` at line 277 is called with an argument built by `JSON.stringify(body)` (line 277), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:277
`debug` at line 310 is called with an argument built by `JSON.stringify(svcPostSearchPayload)` (line 310), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:310
`debug` at line 312 is called with an argument built by `JSON.stringify(response)` (line 312), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:312
`debug` at line 316 is called with an argument built by `JSON.stringify(body)` (line 316), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_asset-event-handler/index.js:316
`debug` at line 37 is called with an argument built by `JSON.stringify(event)` (line 37), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_assets/index.js:37
`debug` at line 64 is called with an argument built by `JSON.stringify(data)` (line 64), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_assets/index.js:64
`debug` at line 77 is called with an argument built by `JSON.stringify(res)` (line 77), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_assets/index.js:77
`debug` at line 81 is called with an argument built by `JSON.stringify(error)` (line 81), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_assets/index.js:81
`debug` at line 89 is called with an argument built by `JSON.stringify(res)` (line 89), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_assets/index.js:89
`debug` at line 105 is called with an argument built by `JSON.stringify(res)` (line 105), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_assets/index.js:105
`debug` at line 49 is called with an argument built by `JSON.stringify(query)` (line 49), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — core/jazz_assets/components/crud/getList.js:49

What to do

Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped2.7 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

`html` is text this program did not author, and it is written into the text of an element through Angular's `bypassSecurityTrustHtml` 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. — core/jazz_ui/src/app/core/pipes/safe-html.pipe.ts:9
`html` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through Angular's `bypassSecurityTrustUrl` 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. — core/jazz_ui/src/app/core/pipes/safe-url.pipe.ts:9

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.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element3.5 / 10Weak✓ Tool-verified

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.

This loop runs once per element of `new_keys`, and the statement it guards acts on the element it is on — `new_keys[i]`. The test deciding whether that statement runs does not: `old_keys.indexOf(new_keys[0]) >= 0` reads `new_keys[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — core/jazz_services/components/utils.js:180

What to do

Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.

Do you agree with this assessment?

X3 · Exception handling5.3 / 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. (×40) — core/jazz_acl/components/logger.js:32, core/jazz_admin/components/utils.js:69, core/jazz_admin/components/utils.js:77, …

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X5 · Nullable reference types2.0 / 10Critical✓ 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.

0/12 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.

What to do

The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

Do you agree with this assessment?

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.

Lens	Score	Rating	Impact
Code Health	50%	Weak — gated by R1, X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	65%	Adequate — gated by AX10	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	63%	Adequate — gated by D34	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	45%	Weak — gated by D9, D13, R8	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	59%	Adequate — gated by D28, D29, D30, D43	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	60%	Adequate	Strongest area.

Unscored — 4 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.

D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

C3 Audit Trail — Not assessed: these audit 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 audit 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.
C4 Data Retention — Not assessed: these retention 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 retention 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.
C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 48 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.

AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — Not applicable: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization 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 authorization 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.
D12 Dependency Hygiene — Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 13 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D18 Solution Shape — D18 scores the shape of a .NET solution, but this repository's production source is mostly .go, .groovy, .java, .py, .ts — the .NET project files present are an immaterial minority — so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — the repository wires up no coverage collector for `--collect:"XPlat Code Coverage"` to use; the JavaScript/TypeScript half measured 76.7% (mocha in core/jazz_acl/: not run; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_admin/; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_apigee-proxy-aws/; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_asset-event-handler/; mocha in core/jazz_assets/: not run; mocha in core/jazz_cloud-logs-streamer/: not run; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_codeq/; mocha in core/jazz_cognito-admin-authorizer/: not run; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_cognito-authorizer/; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_create-serverless-service/; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_delete-serverless-service/; mocha in core/jazz_deployments/: not run). This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 CQRS handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 7 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
X2 Cancellation propagation — no C# was loaded; this repository's Java and Python were read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
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.
X4 Structured logging — 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
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 — 76 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×24

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×14

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D28 · Secrets (history) · High secret · ×13

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D13 · Secret Scanning · Leaked secret · ×3

REDACTED
REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import 'aws-sdk' · ×3

Unlisted import 'aws-sdk' core/jazz_admin/components/utils.js:26 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'aws-sdk' core/jazz_metrics/components/utils.js:28 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'aws-sdk' core/jazz_token-authorizer/index.js:24 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

D10 · Test Quality · Assertions commented out · ×2

Assertions commented out: Verify METRICS COUNT for Website core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts:177 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: Verify METRICS COUNT for Website in Test Branch core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts:348 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · Critical vulnerability · ×1

REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×1

REDACTED

R8 · Dependency Hygiene · Unlisted import 'uuid' · ×1

Unlisted import 'uuid' core/jazz_metrics/components/utils.js:29 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'd3-array' · ×1

Unlisted import 'd3-array' core/jazz_ui/src/app/secondary-components/bar-graph/bar-graph.component.ts:5 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'd3-axis' · ×1

Unlisted import 'd3-axis' core/jazz_ui/src/app/secondary-components/bar-graph/bar-graph.component.ts:6 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'd3-scale' · ×1

Unlisted import 'd3-scale' core/jazz_ui/src/app/secondary-components/bar-graph/bar-graph.component.ts:4 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'd3-selection' · ×1

Unlisted import 'd3-selection' core/jazz_ui/src/app/secondary-components/bar-graph/bar-graph.component.ts:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'd3-shape' · ×1

Unlisted import 'd3-shape' core/jazz_ui/src/app/secondary-components/line-graph/line-graph.component.ts:5 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'd3-time' · ×1

Unlisted import 'd3-time' core/jazz_ui/src/app/secondary-components/line-graph/line-graph.component.ts:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'd3-time-format' · ×1

Unlisted import 'd3-time-format' core/jazz_ui/src/app/secondary-components/line-graph/line-graph.component.ts:7 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'moment' · ×1

Unlisted import 'moment' core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.ts:13 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'selenium-webdriver' · ×1

Unlisted import 'selenium-webdriver' core/jazz_ui/e2e/04-apiservices/apiservices.e2e-spec.ts:17 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

Serious — 554 finding(s)

D10 · Test Quality · No assertions · ×40

No assertions: backtologin core/jazz_ui/e2e/01-register/register.e2e-spec.ts:34 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: register core/jazz_ui/e2e/01-register/register.e2e-spec.ts:56 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: forgotpassword core/jazz_ui/e2e/02-forgotpassword/forgotpassword.e2e-spec.ts:28 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify API Deployments core/jazz_ui/e2e/04-apiservices/apiservices.e2e-spec.ts:197 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify API Asset core/jazz_ui/e2e/04-apiservices/apiservices.e2e-spec.ts:201 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify API Logs core/jazz_ui/e2e/04-apiservices/apiservices.e2e-spec.ts:206 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify API Deployments for Test Branch core/jazz_ui/e2e/04-apiservices/apiservices.e2e-spec.ts:415 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify API Asset for Test Branch core/jazz_ui/e2e/04-apiservices/apiservices.e2e-spec.ts:419 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify API Logs for Test Branch core/jazz_ui/e2e/04-apiservices/apiservices.e2e-spec.ts:423 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Lambda Deployments core/jazz_ui/e2e/05-lambdaservices/lambdaservices.e2e-spec.ts:170 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Lambda Asset core/jazz_ui/e2e/05-lambdaservices/lambdaservices.e2e-spec.ts:174 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Lambda Logs core/jazz_ui/e2e/05-lambdaservices/lambdaservices.e2e-spec.ts:178 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Identifying Environment and Navigation for Lambda core/jazz_ui/e2e/05-lambdaservices/lambdaservices.e2e-spec.ts:193 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Lambda Deployments for Test Branch core/jazz_ui/e2e/05-lambdaservices/lambdaservices.e2e-spec.ts:339 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Lambda Asset for Test Branch core/jazz_ui/e2e/05-lambdaservices/lambdaservices.e2e-spec.ts:343 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Lambda Logs for Test Branch core/jazz_ui/e2e/05-lambdaservices/lambdaservices.e2e-spec.ts:347 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Website Deployments core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts:168 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Wesbsite Asset core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts:172 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Identifying Environment and Navigation for Website core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts:189 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Website Deployments for Test Branch core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts:340 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify Wesbsite Asset for Test Branch core/jazz_ui/e2e/06-websiteservices/websiteservices.e2e-spec.ts:344 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify SLS-App Deployments core/jazz_ui/e2e/07-slsappservices/slsappservices.e2e-spec.ts:129 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify SLS-App Asset core/jazz_ui/e2e/07-slsappservices/slsappservices.e2e-spec.ts:133 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify SLS-App Logs core/jazz_ui/e2e/07-slsappservices/slsappservices.e2e-spec.ts:138 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Verify SLS-App Deployments for Test Branch core/jazz_ui/e2e/07-slsappservices/slsappservices.e2e-spec.ts:274 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 15 more in this group — see findings.md.

R4 · Test Coverage · No test reaches this file · ×40

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 core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/jazz_token-authorizer/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 core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.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 core/jazz_cognito-authorizer/components/auth-policy.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 core/jazz_cognito-authorizer/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 core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/directives/slimscroll.directive.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 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 core/jazz_ui/src/app/pages/landing/landing.component.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 core/jazz_ui/src/app/pages/environment-codequality/env-codequality-section.component.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 core/jazz_ui/src/app/secondary-components/overview-sidebar/overview-sidebar.component.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 core/jazz_ui/src/app/shared-module/shared.module.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 core/jazz_ui/src/app/pages/service-metrics/data.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 templates/react-website-template/app/src/serviceWorker.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 core/jazz_ui/src/app/pages/admin-dashboard/admin-dashboard.component.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/jazz_ui/src/app/primary-components/filter-tag/filter-tag.component.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 core/jazz_ui/src/app/primary-components/json-viewer/json-viewer.component.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 core/jazz_ui/src/app/core/pipes/order-by.pipe.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 core/jazz_cognito-admin-authorizer/components/logger.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 core/jazz_token-authorizer/components/logger.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 builds/jazz_azure-create-service/components/ClientFactory.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 builds/jazz_azure-create-service/components/FunctionApp.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.
+ 15 more in this group — see findings.md.

X3 · Exception handling · Swallowed exception (empty catch) · ×40

Swallowed exception (empty catch) core/jazz_acl/components/logger.js:32 — 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) core/jazz_admin/components/utils.js:69 — 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) core/jazz_admin/components/utils.js:77 — 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) core/jazz_admin/components/logger.js:32 — 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) core/jazz_apigee-proxy-aws/components/logger.js:32 — 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) core/jazz_asset-event-handler/components/logger.js:32 — 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) core/jazz_assets/components/utils.js:126 — 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) core/jazz_assets/components/utils.js:134 — 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) core/jazz_assets/components/logger.js:32 — 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) core/jazz_cloud-logs-streamer/components/logger.js:32 — 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) core/jazz_codeq/components/logger.js:33 — 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) core/jazz_cognito-admin-authorizer/components/logger.js:32 — 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) core/jazz_cognito-authorizer/components/logger.js:33 — 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) core/jazz_create-serverless-service/components/logger.js:33 — 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) core/jazz_delete-serverless-service/components/logger.js:32 — 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) core/jazz_deployments-event-handler/components/logger.js:32 — 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) core/jazz_deployments/components/logger.js:33 — 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) core/jazz_email/components/logger.js:32 — 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) core/jazz_environment-event-handler/components/logger.js:33 — 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) core/jazz_environments/components/utils.js:105 — 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) core/jazz_environments/components/logger.js:33 — 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) core/jazz_es-kinesis-log-streamer/components/logger.js:33 — 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) core/jazz_events-handler/components/logger.js:33 — 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) core/jazz_events/components/logger.js:33 — 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) core/jazz_is-service-available/components/logger.js:33 — 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.
+ 15 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Medium CVE · ×14

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D3 · God Classes · FileTooLong · ×10

FileTooLong: js/bootstrap.js core/jazz-web/js/bootstrap.js — FileTooLong — 1337 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 837 over it, 2.67× 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/bootstrap.js templates/static-website-template/app/js/bootstrap.js — FileTooLong — 1337 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 837 over it, 2.67× 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: service-overview/service-overview.component.ts core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts — FileTooLong — 1131 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 631 over it, 2.26× 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 — 890 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: CreateServiceComponent (34-1304). The bar is 500 significant lines; this is 390 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: REDACTED REDACTED — FileTooLong — 650 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ServiceLogsComponent (26-916). The bar is 500 significant lines; this is 150 over it, 1.30× 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: environment-overview/env-overview-section.component.ts core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts — FileTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: EnvOverviewSectionComponent (15-866). The bar is 500 significant lines; this is 148 over it, 1.30× 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: service-metrics/service-metrics.component.ts core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts — FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ServiceMetricsComponent (21-820). The bar is 500 significant lines; this is 113 over it, 1.23× 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: service-cost/service-cost.component.ts core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts — FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ServiceCostComponent (25-831). The bar is 500 significant lines; this is 90 over it, 1.18× 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: environment-logs/env-logs-section.component.ts core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts — FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: EnvLogsSectionComponent (25-794). The bar is 500 significant lines; this is 62 over it, 1.12× 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: jazz_metrics/index.js core/jazz_metrics/index.js — FileTooLong — 522 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 22 over it, 1.04× 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.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

R11 · Import Boundaries · Boundary violation [package · ×9

Boundary violation [package:relative-cross-package] core/jazz_ui/src/app/environment-module/environment.module.ts:12 — core/jazz_ui/src/app/environment-module/environment.module.ts:12 reaches into another package with a relative path (../primary-components/daterange-picker/ng2-datepicker) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/jazz_ui/src/app/primary-components/daterange-picker/daterange-picker.component.ts:2 — core/jazz_ui/src/app/primary-components/daterange-picker/daterange-picker.component.ts:2 reaches into another package with a relative path (./ng2-datepicker) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.d.ts:3 — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.d.ts:3 reaches into another package with a relative path (../../ng2-slimscroll) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.module.js:4 — core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.module.js:4 reaches into another package with a relative path (../../ng2-slimscroll) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/jazz_ui/src/app/service-module/service.module.imports.common.ts:5 — core/jazz_ui/src/app/service-module/service.module.imports.common.ts:5 reaches into another package with a relative path (../primary-components/daterange-picker/ng2-datepicker) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/jazz_ui/src/app/service-module/service.module.ts:21 — core/jazz_ui/src/app/service-module/service.module.ts:21 reaches into another package with a relative path (../primary-components/daterange-picker/ng2-datepicker) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/jazz_ui/src/app/shared-module/shared.module.ts:36 — core/jazz_ui/src/app/shared-module/shared.module.ts:36 reaches into another package with a relative path (../primary-components/daterange-picker/ng2-datepicker) — import the package by name instead.
Boundary violation [package:third-party-deep-import] core/jazz_ui/src/polyfills.ts:19 — core/jazz_ui/src/polyfills.ts:19 imports zone.js/dist/zone, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] templates/angular-website-template/app/src/polyfills.ts:58 — templates/angular-website-template/app/src/polyfills.ts:58 imports zone.js/dist/zone, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.

D3 · God Classes · TooManyMethods · ×7

TooManyMethods: ServiceOverviewComponent core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:23 — TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.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.
TooManyMethods: CreateServiceComponent REDACTED:26 — TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.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.
TooManyMethods: EnvOverviewSectionComponent core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:9 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: ResourceFactory REDACTED:15 — 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: ServiceCostComponent core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:17 — 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: ServiceLogsComponent REDACTED:21 — 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: EnvLogsSectionComponent core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:19 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.

D3 · God Classes · ClassTooLong · ×7

ClassTooLong: CreateServiceComponent REDACTED:26 — ClassTooLong — 867 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. The bar is 400 significant lines; this is 467 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.
ClassTooLong: ServiceLogsComponent REDACTED:21 — ClassTooLong — 630 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 230 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EnvOverviewSectionComponent core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:9 — ClassTooLong — 625 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 225 over it, 1.56× 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: ServiceMetricsComponent core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:16 — ClassTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 195 over it, 1.49× 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: ServiceCostComponent core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:17 — ClassTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 172 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.
ClassTooLong: EnvLogsSectionComponent core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:19 — ClassTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 142 over it, 1.36× 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: ServicesListComponent core/jazz_ui/src/app/pages/services-list/services-list.component.ts:23 — ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 74 over it, 1.19× 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.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D3 · God Classes · FunctionTooLong · ×4

FunctionTooLong: index.handler core/jazz_t-vault/index.js:37 — FunctionTooLong — handler runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× 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.handler core/jazz_usermanagement/index.js:36 — FunctionTooLong — handler runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.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: index.getServiceData core/jazz_create-serverless-service/index.js:316 — FunctionTooLong — getServiceData runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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.handler core/jazz_create-serverless-service/index.js:38 — FunctionTooLong — handler runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

IC1 · Incompleteness & stubs · Both branches are identical · ×4

Both branches are identical — the condition decides nothing core/jazz_services/components/utils.js:180 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing core/jazz_ui/src/app/core/services/request.service.ts:113 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing core/jazz_ui/src/app/core/services/request.service.ts:154 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing core/jazz_ui/src/app/core/services/request.service.ts:195 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.

R7 · Dead Code · Dead file (~8 LoC) · ×4

Dead file (~8 LoC) builds/jazz_azure-create-service/components/Utils.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~8 LoC) core/jazz_ui/src/config/templates/go-yaml.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (REDACTED, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~8 LoC) core/jazz_ui/src/config/templates/nodejs-yaml.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (REDACTED, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~8 LoC) core/jazz_ui/src/config/templates/python-yaml.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (REDACTED, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

D2 · Cognitive Complexity · exports · ×3

exports::getServiceData (cognitive 26) core/jazz_create-serverless-service/components/crud/create.js:40 — exports::getServiceData has cognitive complexity 26 (threshold 15). Drivers by points: if/else 21 (24 pts), boolean chains 2 (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.
exports::getServiceData (cognitive 22) core/jazz_services-handler/components/crud/update.js:50 — exports::getServiceData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 2 (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.
exports::getServiceData (cognitive 18) core/jazz_create-serverless-service/components/crud/update.js:41 — exports::getServiceData has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2 (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.

D29 · Static Analysis (SAST) · REDACTED · ×3

REDACTED
REDACTED
REDACTED

D3 · God Classes · MethodTooLong · ×3

MethodTooLong: ServiceMetricsComponent.applyFilter core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:416 — MethodTooLong — applyFilter runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: CreateServiceComponent.createService REDACTED:667 — MethodTooLong — createService runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: ChartjsLinegraphComponent.getOptions core/jazz_ui/src/app/secondary-components/chartjs-linegraph/chartjs-linegraph.component.ts:51 — MethodTooLong — getOptions runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D35 · Change Coupling · Change coupling · ×3

Change coupling: env-logs-section.component.ts ↔ REDACTED core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:1 — `core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts` and `REDACTED` change together 74% of the time (28 of the 38 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 28 shared commits counted here, the most recent 3 are `33da7fb0` Remove old resources when yml is updated in custom Apps (#1267); `ea496abe` Address incorrect custom service logs payload (#1210); `97faf1ce` Bugfix/sls app fix (#1205) — run `git show` on any of them.
Change coupling: REDACTED ↔ advanced-filters.component.ts REDACTED:1 — `REDACTED` and `core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts` change together 71% of the time (17 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 17 shared commits counted here, the most recent 3 are `4b67d711` Added support for all service types in asset name filter; `a65a358b` filter changes in metrics and logs; `7a4b29d6` sls-app bug fixes (#1134) — run `git show` on any of them.
Change coupling: env-logs-section.component.ts ↔ advanced-filters.component.ts core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:1 — `core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts` and `core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts` change together 62% of the time (15 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `4b67d711` Added support for all service types in asset name filter; `a65a358b` filter changes in metrics and logs; `07b9117e` changes — run `git show` on any of them.

D4 · Code Duplication · Duplicated block (17 lines × 3) · ×3

Duplicated block (17 lines × 3) templates/api-template-python/components/logger.py:93 — templates/api-template-python/components/logger.py:93-109 | templates/function-template-python/components/logger.py:106-122 | templates/sls-app-template-python/components/logger.py:93-109 — before extracting anything, compare `templates/api-template-python/components/logger.py` and `templates/function-template-python/components/logger.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 92 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 (17 lines × 3) templates/api-template-go/logger.go:18 — templates/api-template-go/logger.go:18-34 | templates/function-template-go/logger.go:18-34 | templates/sls-app-template-go/components/logger.go:21-37 — `templates/api-template-go/logger.go` and `templates/function-template-go/logger.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (17 lines × 3) templates/api-template-go/logger.go:72 — templates/api-template-go/logger.go:72-88 | templates/function-template-go/logger.go:72-88 | templates/sls-app-template-go/components/logger.go:78-94 — `templates/api-template-go/logger.go` and `templates/function-template-go/logger.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

D6 · Cohesion (LCOM4) · Low cohesion · ×3

Low cohesion: TableTemplateComponent (LCOM4 5) core/jazz_ui/src/app/secondary-components/table-template/table-template.component.ts:10 — TableTemplateComponent'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: JazzHeaderComponent (LCOM4 4) core/jazz_ui/src/app/secondary-components/jazz-header/jazz-header.component.ts:17 — JazzHeaderComponent'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: EnvOverviewSectionComponent (LCOM4 4) core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:9 — EnvOverviewSectionComponent'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.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×3

Sync-over-async blocking REDACTED:224 — `fs.readFileSync` in `createOrUpdateApiGatewayWithSwaggerJson` 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:362 — `fs.readFileSync` in `uploadFilesToStorageFromZipBase64` 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 builds/jazz_azure-create-service/index.js:9 — `fs.readFileSync` in `exports` 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.

R7 · Dead Code · Dead file (~33 LoC) · ×3

Dead file (~33 LoC) core/jazz_services-handler/utils/service-creation-events.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~33 LoC) core/jazz_ui/src/app/admin-module/admin.module.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~33 LoC) core/jazz_ui/src/app/service-module/service.route.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (core/jazz_ui/src/app/service-module/service.module.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~31 LoC) · ×3

Dead file (~31 LoC) core/jazz_cognito-admin-authorizer/components/response.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~31 LoC) core/jazz_cognito-authorizer/components/response.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~31 LoC) core/jazz_token-authorizer/components/response.js — no import path from any entry point (53 application, 26 tooling, 114 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

D1 · Cyclomatic Complexity · index.handler (cyclomatic 41) · ×2

index.handler (cyclomatic 41) REDACTED:29 — index.handler has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 10 of the 41 points are its own statements and the rest belongs to 8 function items inside it that branch (AuthPolicy, a function literal at line 119, a function literal at line 315, …). 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.
index.handler (cyclomatic 41) core/jazz_token-authorizer/index.js:29 — index.handler has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 10 of the 41 points are its own statements and the rest belongs to 9 function items inside it that branch (AuthPolicy, a function literal at line 105, 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 · (anonymous) · ×2

(anonymous)::DatePickerOptions (cyclomatic 23) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:16 — (anonymous)::DatePickerOptions has cyclomatic complexity 23 (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.
(anonymous)::generateCalendar (cyclomatic 22) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:158 — (anonymous)::generateCalendar 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 · exports · ×2

exports::getServiceData (cyclomatic 23) core/jazz_create-serverless-service/components/crud/create.js:40 — exports::getServiceData 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.
exports::getServiceData (cyclomatic 19) core/jazz_services-handler/components/crud/update.js:50 — exports::getServiceData 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 · bootstrap.Tooltip.show (cyclomatic 22) · ×2

bootstrap.Tooltip.show (cyclomatic 22) core/jazz-web/js/bootstrap.js:1437 — bootstrap.Tooltip.show has cyclomatic complexity 22 (threshold 15). Of this number, 21 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.
bootstrap.Tooltip.show (cyclomatic 22) templates/static-website-template/app/js/bootstrap.js:1437 — bootstrap.Tooltip.show has cyclomatic complexity 22 (threshold 15). Of this number, 21 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 · handler (cyclomatic 22) · ×2

handler (cyclomatic 22) core/jazz_assets/index.js:33 — handler has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 72, handleResponse, a function literal at line 76, …). 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.
handler (cyclomatic 22) core/jazz_admin/index.js:31 — handler has cyclomatic complexity 22 (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 · bootstrap.Modal.backdrop (cyclomatic 17) · ×2

bootstrap.Modal.backdrop (cyclomatic 17) core/jazz-web/js/bootstrap.js:1109 — bootstrap.Modal.backdrop has cyclomatic complexity 17 (threshold 15). Of this number, 13 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.
bootstrap.Modal.backdrop (cyclomatic 17) templates/static-website-template/app/js/bootstrap.js:1109 — bootstrap.Modal.backdrop has cyclomatic complexity 17 (threshold 15). Of this number, 13 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.

D2 · Cognitive Complexity · (anonymous) · ×2

(anonymous)::generateCalendar (cognitive 45) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:158 — (anonymous)::generateCalendar has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 12 (29 pts), if/else 6 (11 pts), boolean chains 4, loops 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.
(anonymous)::DatePickerOptions (cognitive 22) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:16 — (anonymous)::DatePickerOptions has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, ternaries 11. 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 · sortUtil (cognitive 33) · ×2

sortUtil (cognitive 33) core/jazz_services/components/utils.js:209 — sortUtil has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 8 (24 pts), if/else 6 (8 pts), boolean chains 1 (nesting depth added 18). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 211, 220). 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.
sortUtil (cognitive 33) core/jazz_environments/components/utils.js:145 — sortUtil has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 8 (24 pts), if/else 6 (8 pts), boolean chains 1 (nesting depth added 18). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 147, 156). 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 · bootstrap.Tooltip.show (cognitive 25) · ×2

bootstrap.Tooltip.show (cognitive 25) core/jazz-web/js/bootstrap.js:1437 — bootstrap.Tooltip.show has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 8, ternaries 3 (6 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 2 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.
bootstrap.Tooltip.show (cognitive 25) templates/static-website-template/app/js/bootstrap.js:1437 — bootstrap.Tooltip.show has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 8, ternaries 3 (6 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 2 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.genericInputValidation (cognitive 25) · ×2

index.genericInputValidation (cognitive 25) core/jazz_environments/index.js:170 — index.genericInputValidation has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 15, if/else 9 (10 pts) (nesting depth added 1). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 171). 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.
index.genericInputValidation (cognitive 25) core/jazz_slack-channel/index.js:63 — index.genericInputValidation has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 7). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 65). 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 · bootstrap.Modal.backdrop (cognitive 23) · ×2

bootstrap.Modal.backdrop (cognitive 23) core/jazz-web/js/bootstrap.js:1109 — bootstrap.Modal.backdrop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 4 (7 pts), boolean chains 5 (nesting depth added 7). Of this number, 16 points are the body's own statements and 7 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.
bootstrap.Modal.backdrop (cognitive 23) templates/static-website-template/app/js/bootstrap.js:1109 — bootstrap.Modal.backdrop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 4 (7 pts), boolean chains 5 (nesting depth added 7). Of this number, 16 points are the body's own statements and 7 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 · update.default · ×2

update.default::getServiceData (cognitive 22) core/jazz_services-handler/components/crud/update.js:50 — update.default::getServiceData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 2 (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.
update.default::getServiceData (cognitive 18) core/jazz_create-serverless-service/components/crud/update.js:41 — update.default::getServiceData has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2 (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 · bootstrap.Affix.getState (cognitive 18) · ×2

bootstrap.Affix.getState (cognitive 18) core/jazz-web/js/bootstrap.js:2257 — bootstrap.Affix.getState has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 5 (6 pts), boolean chains 3 (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.
bootstrap.Affix.getState (cognitive 18) templates/static-website-template/app/js/bootstrap.js:2257 — bootstrap.Affix.getState has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 5 (6 pts), boolean chains 3 (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.

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2

Duplicated block (10 lines × 2) templates/api-template-java/src/main/java/com/slf/util/ErrorUtil.java:20 — templates/api-template-java/src/main/java/com/slf/util/ErrorUtil.java:20-29 | templates/function-template-java/src/main/java/com/slf/util/ErrorUtil.java:19-28 — before extracting anything, compare `templates/api-template-java/src/main/java/com/slf/util/ErrorUtil.java` and `templates/function-template-java/src/main/java/com/slf/util/ErrorUtil.java` as WHOLE FILES: 95% 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. Read the line range as the matched WINDOW rather than a finished unit: at `templates/api-template-java/src/main/java/com/slf/util/ErrorUtil.java:20` 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `templates/api-template-java/src/main/java/com/slf/util/ErrorUtil.java:19` calls `put` and `templates/function-template-java/src/main/java/com/slf/util/ErrorUtil.java:18` 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 (10 lines × 2) templates/api-template-java/src/main/java/com/slf/util/JsonUtil.java:13 — templates/api-template-java/src/main/java/com/slf/util/JsonUtil.java:13-22 | templates/function-template-java/src/main/java/com/slf/util/JsonUtil.java:13-22 — before extracting anything, compare `templates/api-template-java/src/main/java/com/slf/util/JsonUtil.java` and `templates/function-template-java/src/main/java/com/slf/util/JsonUtil.java` 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.

R10 · Code Duplication · Duplicated block with local edits (97 matched lines × 2 locations) · ×2

Duplicated block with local edits (97 matched lines × 2 locations) core/jazz_environments/components/utils.js:51 — core/jazz_environments/components/utils.js:51 · core/jazz_services/components/utils.js:47 — the two spans are one implementation copied and then locally edited — 625 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (97 matched lines × 2 locations) core/jazz_environments/components/validation/common.js:69 — core/jazz_environments/components/validation/common.js:69 · core/jazz_services/components/validation/common.js:170 — the two spans are one implementation copied and then locally edited — 488 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 (34 lines × 2 locations) · ×2

Duplicated block (34 lines × 2 locations) core/jazz_asset-event-handler/index.js:209 — core/jazz_asset-event-handler/index.js:209 · core/jazz_asset-event-handler/index.js:255 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (34 lines × 2 locations) core/jazz_asset-event-handler/utils/utils.js:20 — core/jazz_asset-event-handler/utils/utils.js:20 · core/jazz_environment-event-handler/utils/utils.js:20 — 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.

R7 · Dead Code · Dead file (~59 LoC) · ×2

Dead file (~59 LoC) core/jazz_asset-event-handler/utils/utils.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~59 LoC) core/jazz_environment-event-handler/utils/utils.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~39 LoC) · ×2

Dead file (~39 LoC) core/jazz-web/js/ie10-viewport-bug-workaround.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~39 LoC) templates/static-website-template/app/js/ie10-viewport-bug-workaround.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~19 LoC) · ×2

Dead file (~19 LoC) builds/jazz-build-module/apigee/templates/coreAPI_default/Common/resources/jsc/cf_CORS.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~19 LoC) builds/jazz-build-module/apigee/templates/coreAPI_secure/Common/resources/jsc/cf_CORS.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~17 LoC) · ×2

Dead file (~17 LoC) builds/azure-config-pack/nodejs/index.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~17 LoC) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/classes/slimscroll-options.class.js — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~9 LoC) · ×2

Dead file (~9 LoC) core/jazz_ui/src/app/pages/services-list/service-list.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~9 LoC) core/jazz_ui/src/app/service-module/service.module.imports.common.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

X1 · Async correctness · `async` callback passed to `forEach` · ×2

`async` callback passed to `forEach` REDACTED:185 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` REDACTED:212 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.

X1 · Async correctness · `async` Promise executor · ×2

`async` Promise executor core/jazz_metrics/index.js:646 — The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor core/jazz_metrics/index.js:696 — The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.

X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×2

Untrusted text written into markup unescaped core/jazz_ui/src/app/core/pipes/safe-html.pipe.ts:9 — `html` is text this program did not author, and it is written into the text of an element through Angular's `bypassSecurityTrustHtml` 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 core/jazz_ui/src/app/core/pipes/safe-url.pipe.ts:9 — `html` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through Angular's `bypassSecurityTrustUrl` 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.

D1 · Cyclomatic Complexity · handler (cyclomatic 72) · ×1

handler (cyclomatic 72) core/jazz_t-vault/index.js:37 — handler has cyclomatic complexity 72 (threshold 15). Of this number, 49 points are the body's own statements and 23 belong to 75 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 · handler (cyclomatic 50) · ×1

handler (cyclomatic 50) core/jazz_create-serverless-service/index.js:38 — handler has cyclomatic complexity 50 (threshold 15). Of this number, 47 points are the body's own statements and 3 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 · index.getServiceData (cyclomatic 49) · ×1

index.getServiceData (cyclomatic 49) core/jazz_create-serverless-service/index.js:316 — index.getServiceData has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 1 of the 49 points is its own statement and the rest belongs to one function literal inside it that branches (line 317). 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 · CreateServiceComponent.createService (cyclomatic 41) · ×1

CreateServiceComponent.createService (cyclomatic 41) REDACTED:667 — CreateServiceComponent.createService has cyclomatic complexity 41 (threshold 15). Of this number, 38 points are the body's own statements and 3 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 · index.handler (cyclomatic 37) · ×1

index.handler (cyclomatic 37) core/jazz_services/index.js:34 — index.handler has cyclomatic complexity 37 (threshold 15). Of this number, 24 points are the body's own statements and 13 belong to 8 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 · handler (cyclomatic 35) · ×1

handler (cyclomatic 35) core/jazz_usermanagement/index.js:36 — handler has cyclomatic complexity 35 (threshold 15). Of this number, 25 points are the body's own statements and 10 belong to 19 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 · handler (cyclomatic 34) · ×1

handler (cyclomatic 34) core/jazz_deployments/index.js:37 — handler has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 47, 78, 112, …). 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 · ServiceMetricsComponent.applyFilter (cyclomatic 33) · ×1

ServiceMetricsComponent.applyFilter (cyclomatic 33) core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:416 — ServiceMetricsComponent.applyFilter has cyclomatic complexity 33 (threshold 15). 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, 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 · utils.getNotificationMessage (cyclomatic 32) · ×1

utils.getNotificationMessage (cyclomatic 32) core/jazz_slack-event-handler/components/utils.js:19 — utils.getNotificationMessage 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 · CreateServiceComponent.disableForm (cyclomatic 32) · ×1

CreateServiceComponent.disableForm (cyclomatic 32) REDACTED:977 — CreateServiceComponent.disableForm has cyclomatic complexity 32 (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 · handler (cyclomatic 31) · ×1

handler (cyclomatic 31) core/jazz_environments/index.js:34 — handler has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 47, 113, 139, …). 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.handler (cyclomatic 30) · ×1

index.handler (cyclomatic 30) core/jazz_logs/index.js:34 — index.handler has cyclomatic complexity 30 (threshold 15). Of this number, 26 points are the body's own statements and 4 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 · index.genericInputValidation (cyclomatic 29) · ×1

index.genericInputValidation (cyclomatic 29) core/jazz_environments/index.js:170 — index.genericInputValidation has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to one function literal inside it that branches (line 171). 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 · getList.default (cyclomatic 28) · ×1

getList.default (cyclomatic 28) core/jazz_services/components/crud/getList.js:27 — getList.default has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 103, a function literal at line 46, appendPolicies). 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 · ServiceOverviewComponent.check_empty_fields (cyclomatic 28) · ×1

ServiceOverviewComponent.check_empty_fields (cyclomatic 28) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:758 — ServiceOverviewComponent.check_empty_fields has cyclomatic complexity 28 (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 · exports (cyclomatic 28) · ×1

exports (cyclomatic 28) core/jazz_services/components/crud/getList.js:27 — exports has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 103, a function literal at line 46, appendPolicies, …). 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.processACLRequest (cyclomatic 25) · ×1

index.processACLRequest (cyclomatic 25) core/jazz_acl/index.js:55 — index.processACLRequest 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 · index.bitbucketScmContextDetails (cyclomatic 25) · ×1

index.bitbucketScmContextDetails (cyclomatic 25) core/jazz_scm-webhook/index.js:129 — index.bitbucketScmContextDetails has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to one function literal inside it that branches (line 131). 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 · create.default · ×1

create.default::getServiceData (cyclomatic 23) core/jazz_create-serverless-service/components/crud/create.js:40 — create.default::getServiceData 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 · ServiceOverviewComponent.ngOnChanges (cyclomatic 23) · ×1

ServiceOverviewComponent.ngOnChanges (cyclomatic 23) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1190 — ServiceOverviewComponent.ngOnChanges has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · SlimScrollOptions.constructor (cyclomatic 23) · ×1

SlimScrollOptions.constructor (cyclomatic 23) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/classes/slimscroll-options.class.ts:28 — SlimScrollOptions.constructor has cyclomatic complexity 23 (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 · manageProcessItem (cyclomatic 22) · ×1

manageProcessItem (cyclomatic 22) core/jazz_environment-event-handler/index.js:190 — manageProcessItem has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 19 function literals inside it that branch (lines 191, 246, 206, …). 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.gitlabScmContextDetails (cyclomatic 21) · ×1

index.gitlabScmContextDetails (cyclomatic 21) core/jazz_scm-webhook/index.js:205 — index.gitlabScmContextDetails has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 207). 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 · ServiceOverviewComponent.generateExpression (cyclomatic 21) · ×1

ServiceOverviewComponent.generateExpression (cyclomatic 21) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:308 — ServiceOverviewComponent.generateExpression 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 · index.genericInputValidation (cyclomatic 20) · ×1

index.genericInputValidation (cyclomatic 20) core/jazz_deployments/index.js:173 — index.genericInputValidation has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 175). 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 · OrderByPipe.transform (cyclomatic 20) · ×1

OrderByPipe.transform (cyclomatic 20) core/jazz_ui/src/app/core/pipes/order-by.pipe.ts:5 — OrderByPipe.transform has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 8, 36). 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 · ServicesListComponent.onFilter (cyclomatic 20) · ×1

ServicesListComponent.onFilter (cyclomatic 20) core/jazz_ui/src/app/pages/services-list/services-list.component.ts:330 — ServicesListComponent.onFilter 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 · ServicesListComponent.onFilterCancel (cyclomatic 20) · ×1

ServicesListComponent.onFilterCancel (cyclomatic 20) core/jazz_ui/src/app/pages/services-list/services-list.component.ts:477 — ServicesListComponent.onFilterCancel 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 · sortUtil (cyclomatic 20) · ×1

sortUtil (cyclomatic 20) core/jazz_deployments/components/utils.js:151 — sortUtil has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 153, 162, 171). 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.genericInputValidation (cyclomatic 19) · ×1

index.genericInputValidation (cyclomatic 19) core/jazz_assets/index.js:143 — index.genericInputValidation 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 145). 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 · update.default · ×1

update.default::getServiceData (cyclomatic 19) core/jazz_services-handler/components/crud/update.js:50 — update.default::getServiceData 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 · ServiceDetailComponent.processService (cyclomatic 19) · ×1

ServiceDetailComponent.processService (cyclomatic 19) core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts:103 — ServiceDetailComponent.processService 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 · ServiceOverviewComponent.serviceDeletionStatus (cyclomatic 19) · ×1

ServiceOverviewComponent.serviceDeletionStatus (cyclomatic 19) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1284 — ServiceOverviewComponent.serviceDeletionStatus has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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 · getLambdaLogsData (cyclomatic 19) · ×1

getLambdaLogsData (cyclomatic 19) REDACTED:208 — getLambdaLogsData has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 223, 262, 211, …). 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 · update.default (cyclomatic 18) · ×1

update.default (cyclomatic 18) core/jazz_create-serverless-service/components/crud/update.js:19 — update.default has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function items inside it that branch (getServiceData, a function literal at line 30). 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 · OnlyNumber.onKeyDown (cyclomatic 18) · ×1

OnlyNumber.onKeyDown (cyclomatic 18) core/jazz_ui/src/app/secondary-components/create-service/onlyNumbers.ts:12 — OnlyNumber.onKeyDown has cyclomatic complexity 18 (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 · JenkinsStatusComponent.makeRequest (cyclomatic 18) · ×1

JenkinsStatusComponent.makeRequest (cyclomatic 18) core/jazz_ui/src/app/pages/jenkins-status/jenkins-status.component.ts:116 — JenkinsStatusComponent.makeRequest has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 120). 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 · ChartjsLinegraphComponent.getOptions (cyclomatic 18) · ×1

ChartjsLinegraphComponent.getOptions (cyclomatic 18) core/jazz_ui/src/app/secondary-components/chartjs-linegraph/chartjs-linegraph.component.ts:51 — ChartjsLinegraphComponent.getOptions has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · CreateServiceComponent.onScroll (cyclomatic 18) · ×1

CreateServiceComponent.onScroll (cyclomatic 18) REDACTED:1119 — CreateServiceComponent.onScroll 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 · exports (cyclomatic 18) · ×1

exports (cyclomatic 18) core/jazz_create-serverless-service/components/crud/update.js:19 — exports has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function items inside it that branch (getServiceData, a function literal at line 30). 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.handler (cyclomatic 17) · ×1

index.handler (cyclomatic 17) core/jazz_delete-serverless-service/index.js:35 — index.handler has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 3 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.formatService (cyclomatic 17) · ×1

utils.formatService (cyclomatic 17) core/jazz_services/components/utils.js:63 — utils.formatService has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (parseValue, a function literal at line 116). 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.genericInputValidation (cyclomatic 17) · ×1

index.genericInputValidation (cyclomatic 17) core/jazz_slack-channel/index.js:63 — index.genericInputValidation has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 65). 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 · CreateServiceComponent.generateExpression (cyclomatic 17) · ×1

CreateServiceComponent.generateExpression (cyclomatic 17) REDACTED:1258 — CreateServiceComponent.generateExpression 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 · handler (cyclomatic 17) · ×1

handler (cyclomatic 17) core/jazz_codeq/index.js:25 — handler 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 6 function literals inside it that branch (lines 37, 68, 63, …). 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 · utils.formatResponse (cyclomatic 16) · ×1

utils.formatResponse (cyclomatic 16) core/jazz_assets/components/utils.js:89 — utils.formatResponse 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 items inside it that branch (parseValue, a function literal at line 142). 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 · utils.getUpdateData (cyclomatic 16) · ×1

utils.getUpdateData (cyclomatic 16) core/jazz_services/components/utils.js:148 — utils.getUpdateData 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 · common.validateDataTypes (cyclomatic 16) · ×1

common.validateDataTypes (cyclomatic 16) core/jazz_services/components/validation/common.js:105 — common.validateDataTypes 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.

D10 · Test Quality · Test project verifies nothing · ×1

Test project verifies nothing: templates/react-website-template/app templates/react-website-template/app/src/App.test.js:5 — No conventional assertion call was detected in 1 of 1 tests in `templates/react-website-template/app` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.

D2 · Cognitive Complexity · index.getServiceData (cognitive 106) · ×1

index.getServiceData (cognitive 106) core/jazz_create-serverless-service/index.js:316 — index.getServiceData has cognitive complexity 106 (threshold 15). Drivers by points: if/else 40 (86 pts), boolean chains 14, error handling 1 (3 pts), loops 1 (3 pts) (nesting depth added 50). None of this is in the body itself: all 106 points belong to one function literal inside it that branches (line 317). 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 · handler (cognitive 106) · ×1

handler (cognitive 106) core/jazz_t-vault/index.js:37 — handler has cognitive complexity 106 (threshold 15). Drivers by points: if/else 37 (60 pts), boolean chains 23, error handling 12 (23 pts) (nesting depth added 34). Of this number, 49 points are the body's own statements and 57 belong to 75 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 · handler (cognitive 81) · ×1

handler (cognitive 81) core/jazz_create-serverless-service/index.js:38 — handler has cognitive complexity 81 (threshold 15). Drivers by points: if/else 35 (59 pts), boolean chains 18, error handling 2, loops 1 (2 pts) (nesting depth added 25). Of this number, 73 points are the body's own statements and 8 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 · handler (cognitive 70) · ×1

handler (cognitive 70) core/jazz_usermanagement/index.js:36 — handler has cognitive complexity 70 (threshold 15). Drivers by points: if/else 25 (51 pts), error handling 7 (13 pts), boolean chains 6 (nesting depth added 32). Of this number, 30 points are the body's own statements and 40 belong to 19 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 · handler (cognitive 64) · ×1

handler (cognitive 64) REDACTED:29 — handler has cognitive complexity 64 (threshold 15). Drivers by points: if/else 35 (47 pts), boolean chains 12, loops 2 (5 pts) (nesting depth added 15). Most of this is not in the body itself: 4 of the 64 points are its own statements and the rest belongs to 16 function items inside it that branch ((anonymous)::getStatementsForEffect, a function literal at line 119, AuthPolicy, …). 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 · index.handler (cognitive 63) · ×1

index.handler (cognitive 63) core/jazz_logs/index.js:34 — index.handler has cognitive complexity 63 (threshold 15). Drivers by points: if/else 23 (45 pts), ternaries 5 (10 pts), loops 1 (4 pts), boolean chains 3, error handling 1 (nesting depth added 30). Of this number, 48 points are the body's own statements and 15 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 · handler (cognitive 63) · ×1

handler (cognitive 63) core/jazz_token-authorizer/index.js:29 — handler has cognitive complexity 63 (threshold 15). Drivers by points: if/else 34 (46 pts), boolean chains 12, loops 2 (5 pts) (nesting depth added 15). Most of this is not in the body itself: 4 of the 63 points are its own statements and the rest belongs to 17 function items inside it that branch ((anonymous)::getStatementsForEffect, a function literal at line 105, AuthPolicy, …). 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 · utils.getNotificationMessage (cognitive 60) · ×1

utils.getNotificationMessage (cognitive 60) core/jazz_slack-event-handler/components/utils.js:19 — utils.getNotificationMessage has cognitive complexity 60 (threshold 15). Drivers by points: if/else 19 (50 pts), boolean chains 8, match/switch 1 (2 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent 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 · CreateServiceComponent.createService (cognitive 60) · ×1

CreateServiceComponent.createService (cognitive 60) REDACTED:667 — CreateServiceComponent.createService has cognitive complexity 60 (threshold 15). Drivers by points: if/else 33 (53 pts), boolean chains 5, error handling 1, loops 1 (nesting depth added 20). Of this number, 57 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 · CreateServiceComponent.onScroll (cognitive 60) · ×1

CreateServiceComponent.onScroll (cognitive 60) REDACTED:1119 — CreateServiceComponent.onScroll has cognitive complexity 60 (threshold 15). Drivers by points: if/else 16 (58 pts), boolean chains 1, loops 1 (nesting depth added 42). 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.handler (cognitive 58) · ×1

index.handler (cognitive 58) core/jazz_services/index.js:34 — index.handler has cognitive complexity 58 (threshold 15). Drivers by points: if/else 33 (46 pts), boolean chains 11, error handling 1 (nesting depth added 13). Of this number, 26 points are the body's own statements and 32 belong to 8 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 · handler (cognitive 58) · ×1

handler (cognitive 58) core/jazz_environments/index.js:34 — handler has cognitive complexity 58 (threshold 15). Drivers by points: if/else 20 (43 pts), error handling 6 (11 pts), boolean chains 4 (nesting depth added 28). Most of this is not in the body itself: 2 of the 58 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 47, 113, 139, …). 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 · handler (cognitive 57) · ×1

handler (cognitive 57) core/jazz_deployments/index.js:37 — handler has cognitive complexity 57 (threshold 15). Drivers by points: if/else 22 (35 pts), error handling 7 (13 pts), boolean chains 9 (nesting depth added 19). Most of this is not in the body itself: 1 of the 57 points is its own statement and the rest belongs to 14 function literals inside it that branch (lines 47, 78, 112, …). 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 · getList.default (cognitive 50) · ×1

getList.default (cognitive 50) core/jazz_services/components/crud/getList.js:27 — getList.default has cognitive complexity 50 (threshold 15). Drivers by points: if/else 18 (35 pts), boolean chains 10, loops 2 (5 pts) (nesting depth added 20). Most of this is not in the body itself: 8 of the 50 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 103, appendPolicies, 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.

D2 · Cognitive Complexity · sortUtil (cognitive 50) · ×1

sortUtil (cognitive 50) core/jazz_deployments/components/utils.js:151 — sortUtil has cognitive complexity 50 (threshold 15). Drivers by points: ternaries 12 (36 pts), if/else 9 (12 pts), boolean chains 2 (nesting depth added 27). Most of this is not in the body itself: 5 of the 50 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 153, 162, 171). 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 · exports (cognitive 50) · ×1

exports (cognitive 50) core/jazz_services/components/crud/getList.js:27 — exports has cognitive complexity 50 (threshold 15). Drivers by points: if/else 18 (35 pts), boolean chains 10, loops 2 (5 pts) (nesting depth added 20). Most of this is not in the body itself: 8 of the 50 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 103, appendPolicies, 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.

D2 · Cognitive Complexity · OrderByPipe.transform (cognitive 47) · ×1

OrderByPipe.transform (cognitive 47) core/jazz_ui/src/app/core/pipes/order-by.pipe.ts:5 — OrderByPipe.transform has cognitive complexity 47 (threshold 15). Drivers by points: if/else 20 (37 pts), error handling 2 (6 pts), boolean chains 4 (nesting depth added 21). Most of this is not in the body itself: 7 of the 47 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 8, 36). 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 · ServiceMetricsComponent.applyFilter (cognitive 41) · ×1

ServiceMetricsComponent.applyFilter (cognitive 41) core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:416 — ServiceMetricsComponent.applyFilter has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (29 pts), match/switch 2 (8 pts), boolean chains 4 (nesting depth added 21). Of this number, 38 points are the body's own statements and 3 belong 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 · ServiceDetailComponent.processService (cognitive 40) · ×1

ServiceDetailComponent.processService (cognitive 40) core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts:103 — ServiceDetailComponent.processService has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (35 pts), boolean chains 5 (nesting depth added 21). To reduce it, split the body into named stages: move each independent 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.processACLRequest (cognitive 39) · ×1

index.processACLRequest (cognitive 39) core/jazz_acl/index.js:55 — index.processACLRequest has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 11 (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 · ServicesListComponent.onFilter (cognitive 39) · ×1

ServicesListComponent.onFilter (cognitive 39) core/jazz_ui/src/app/pages/services-list/services-list.component.ts:330 — ServicesListComponent.onFilter has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (32 pts), boolean chains 6, loops 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 · manageProcessItem (cognitive 37) · ×1

manageProcessItem (cognitive 37) core/jazz_environment-event-handler/index.js:190 — manageProcessItem has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (21 pts), error handling 7 (16 pts) (nesting depth added 15). None of this is in the body itself: all 37 points belong to 19 function literals inside it that branch (lines 191, 246, 206, …). 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 · utils.getUpdateData (cognitive 36) · ×1

utils.getUpdateData (cognitive 36) core/jazz_services/components/utils.js:148 — utils.getUpdateData has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 3 (9 pts), boolean chains 4 (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 · ServicesListComponent.onFilterCancel (cognitive 35) · ×1

ServicesListComponent.onFilterCancel (cognitive 35) core/jazz_ui/src/app/pages/services-list/services-list.component.ts:477 — ServicesListComponent.onFilterCancel has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (28 pts), boolean chains 6, loops 1 (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 · getAuthorizationDetails (cognitive 35) · ×1

getAuthorizationDetails (cognitive 35) core/jazz_cognito-authorizer/index.js:204 — getAuthorizationDetails has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (28 pts), ternaries 1 (4 pts), boolean chains 3 (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 · index.transform (cognitive 33) · ×1

index.transform (cognitive 33) core/jazz_cloud-logs-streamer/index.js:82 — index.transform has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (32 pts), boolean chains 1 (nesting depth added 16). Of this number, 19 points are the body's own statements and 14 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 · validateAssets (cognitive 33) · ×1

validateAssets (cognitive 33) core/jazz_metrics/index.js:308 — validateAssets has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (23 pts), error handling 2 (10 pts) (nesting depth added 19). None of this is in the body itself: all 33 points belong to 9 function literals inside it that branch (lines 315, 374, 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 · getLambdaLogsData (cognitive 33) · ×1

getLambdaLogsData (cognitive 33) REDACTED:208 — getLambdaLogsData has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (26 pts), error handling 5, boolean chains 2 (nesting depth added 12). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 223, 262, 211, …). 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 · handler (cognitive 32) · ×1

handler (cognitive 32) core/jazz_es-kinesis-log-streamer/index.js:32 — handler has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (23 pts), error handling 2 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 18). Most of this is not in the body itself: 6 of the 32 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 60, 46, 57, …). 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 · handler (cognitive 31) · ×1

handler (cognitive 31) core/jazz_splunk-kinesis-log-streamer/index.js:34 — handler has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (17 pts), error handling 2 (6 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (nesting depth added 14). Most of this is not in the body itself: 9 of the 31 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 77, a function literal at line 66, a function literal at line 75, …). 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 · common.validateDataTypes (cognitive 30) · ×1

common.validateDataTypes (cognitive 30) core/jazz_services/components/validation/common.js:105 — common.validateDataTypes has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 5, 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 · CreateServiceComponent.disableForm (cognitive 30) · ×1

CreateServiceComponent.disableForm (cognitive 30) REDACTED:977 — CreateServiceComponent.disableForm has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16, boolean chains 14. 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 · ServiceOverviewComponent.ngOnChanges (cognitive 29) · ×1

ServiceOverviewComponent.ngOnChanges (cognitive 29) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1190 — ServiceOverviewComponent.ngOnChanges has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 5, error handling 1 (2 pts) (nesting depth added 6). Of this number, 21 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · handler (cognitive 29) · ×1

handler (cognitive 29) core/jazz_assets/index.js:33 — handler has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (14 pts), error handling 6 (10 pts), boolean chains 5 (nesting depth added 5). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 72, handleResponse, a function literal at line 76, …). 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 · index.gitlabScmContextDetails (cognitive 28) · ×1

index.gitlabScmContextDetails (cognitive 28) core/jazz_scm-webhook/index.js:205 — index.gitlabScmContextDetails has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 5 (nesting depth added 6). None of this is in the body itself: all 28 points belong to one function literal inside it that branches (line 207). 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 · exports (cognitive 28) · ×1

exports (cognitive 28) core/jazz_deployments/components/crud/getList.js:28 — exports has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 86, a function literal at line 50, scanExecute, …). 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 · JsonEditor.removeJsonList (cognitive 26) · ×1

JsonEditor.removeJsonList (cognitive 26) core/jazz_admin/components/json-editor.js:105 — JsonEditor.removeJsonList has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (26 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 · create.default · ×1

create.default::getServiceData (cognitive 26) core/jazz_create-serverless-service/components/crud/create.js:40 — create.default::getServiceData has cognitive complexity 26 (threshold 15). Drivers by points: if/else 21 (24 pts), boolean chains 2 (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 · getList.default (cognitive 26) · ×1

getList.default (cognitive 26) core/jazz_deployments/components/crud/getList.js:28 — getList.default has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 2 (nesting depth added 9). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 86, 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 · handler (cognitive 26) · ×1

handler (cognitive 26) core/jazz_codeq/index.js:25 — handler has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 3 (5 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 10). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 37, 68, 63, …). 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 · casbin.addOrRemovePolicy (cognitive 25) · ×1

casbin.addOrRemovePolicy (cognitive 25) core/jazz_acl/components/casbin.js:110 — casbin.addOrRemovePolicy has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 3, error handling 1 (nesting depth added 11). 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 · ServiceMetricsComponent.getAssetType (cognitive 25) · ×1

ServiceMetricsComponent.getAssetType (cognitive 25) core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:301 — ServiceMetricsComponent.getAssetType has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 1 (4 pts), boolean chains 1, error handling 1 (nesting depth added 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 313). 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 · getSlackChannelMembers (cognitive 25) · ×1

getSlackChannelMembers (cognitive 25) core/jazz_slack-channel/index.js:408 — getSlackChannelMembers has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (19 pts), error handling 1 (4 pts), loops 1 (2 pts) (nesting depth added 16). None of this is in the body itself: all 25 points belong to 3 function literals inside it that branch (lines 409, 420, 428). 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 · ServiceOverviewComponent.generateExpression (cognitive 24) · ×1

ServiceOverviewComponent.generateExpression (cognitive 24) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:308 — ServiceOverviewComponent.generateExpression has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 4 (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 · ServiceOverviewComponent.modifyEnvArr (cognitive 24) · ×1

ServiceOverviewComponent.modifyEnvArr (cognitive 24) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:884 — ServiceOverviewComponent.modifyEnvArr has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 1 (2 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 · ServiceOverviewMultienvComponent.modifyEnvArr (cognitive 24) · ×1

ServiceOverviewMultienvComponent.modifyEnvArr (cognitive 24) core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts:254 — ServiceOverviewMultienvComponent.modifyEnvArr has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 1 (2 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 · index.handler (cognitive 23) · ×1

index.handler (cognitive 23) core/jazz_delete-serverless-service/index.js:35 — index.handler has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (19 pts), error handling 2, boolean chains 1, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 119, a function literal at line 161, sendEventToHandler). 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 · utils.formatService (cognitive 23) · ×1

utils.formatService (cognitive 23) core/jazz_services/components/utils.js:63 — utils.formatService has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (15 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (parseValue, a function literal at line 116). 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 · ServiceMetricsComponent.setAssetsFilter (cognitive 23) · ×1

ServiceMetricsComponent.setAssetsFilter (cognitive 23) core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:688 — ServiceMetricsComponent.setAssetsFilter has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (22 pts), boolean chains 1 (nesting depth added 14). 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 · ServiceOverviewComponent.check_empty_fields (cognitive 23) · ×1

ServiceOverviewComponent.check_empty_fields (cognitive 23) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:758 — ServiceOverviewComponent.check_empty_fields has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14, boolean chains 9. 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 · CronParser.validateRateExpression (cognitive 23) · ×1

CronParser.validateRateExpression (cognitive 23) core/jazz_create-serverless-service/components/cron-parser.js:146 — CronParser.validateRateExpression has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (22 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 · handler (cognitive 23) · ×1

handler (cognitive 23) core/jazz_admin/index.js:31 — handler has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, error handling 4 (7 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 · utils.formatResponse (cognitive 22) · ×1

utils.formatResponse (cognitive 22) core/jazz_assets/components/utils.js:89 — utils.formatResponse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (15 pts), error handling 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (parseValue, a function literal at line 142). 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 · validate_create_payload.validateEnvironmentExists (cognitive 22) · ×1

validate_create_payload.validateEnvironmentExists (cognitive 22) core/jazz_environments/components/validation/validate_create_payload.js:206 — validate_create_payload.validateEnvironmentExists has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2 (nesting depth added 10). None of this is in the body itself: all 22 points belong to 2 function literals inside it that branch (lines 222, 244). 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.bitbucketScmContextDetails (cognitive 21) · ×1

index.bitbucketScmContextDetails (cognitive 21) core/jazz_scm-webhook/index.js:129 — index.bitbucketScmContextDetails has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, match/switch 1 (nesting depth added 5). None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 131). 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 · common.validateEnumValues (cognitive 21) · ×1

common.validateEnumValues (cognitive 21) core/jazz_services/components/validation/common.js:131 — common.validateEnumValues has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · getList.default (cognitive 20) · ×1

getList.default (cognitive 20) core/jazz_assets/components/crud/getList.js:28 — getList.default has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 93, 52). 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.getEnvironmentLogicalId (cognitive 20) · ×1

index.getEnvironmentLogicalId (cognitive 20) core/jazz_environment-event-handler/index.js:486 — index.getEnvironmentLogicalId has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 11). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 498). 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 · LoginComponent.login (cognitive 20) · ×1

LoginComponent.login (cognitive 20) REDACTED:129 — LoginComponent.login has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5 (nesting depth added 4). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 164, 155). 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 · ChartjsLinegraphComponent.getOptions (cognitive 20) · ×1

ChartjsLinegraphComponent.getOptions (cognitive 20) core/jazz_ui/src/app/secondary-components/chartjs-linegraph/chartjs-linegraph.component.ts:51 — ChartjsLinegraphComponent.getOptions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7, ternaries 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · LandingComponent.shiftLeft (cognitive 20) · ×1

LandingComponent.shiftLeft (cognitive 20) core/jazz_ui/src/app/pages/landing/landing.component.ts:62 — LandingComponent.shiftLeft has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 1 (nesting depth added 11). 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 · EnvOverviewSectionComponent.onRoleNameChange (cognitive 20) · ×1

EnvOverviewSectionComponent.onRoleNameChange (cognitive 20) core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:369 — EnvOverviewSectionComponent.onRoleNameChange has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4 (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 · ServiceAccessControlComponent.isValidData (cognitive 20) · ×1

ServiceAccessControlComponent.isValidData (cognitive 20) core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts:407 — ServiceAccessControlComponent.isValidData has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4 (nesting depth added 7). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 420, 413, 434). 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 · exports (cognitive 20) · ×1

exports (cognitive 20) core/jazz_assets/components/crud/getList.js:28 — exports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 93, a function literal at line 52, a function literal at line 58, …). 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 · handler (cognitive 20) · ×1

handler (cognitive 20) core/jazz_apigee-proxy-aws/index.js:22 — handler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (6 pts), error handling 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 7). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 52, 90, 28). 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.getAssetsDetails (cognitive 19) · ×1

index.getAssetsDetails (cognitive 19) core/jazz_metrics/index.js:252 — index.getAssetsDetails has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2 (nesting depth added 8). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 268). 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 · FilterTagComponent.manageFilters (cognitive 19) · ×1

FilterTagComponent.manageFilters (cognitive 19) core/jazz_ui/src/app/primary-components/filter-tag/filter-tag.component.ts:74 — FilterTagComponent.manageFilters has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (3 pts) (nesting depth added 11). 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 · EnvOverviewSectionComponent.keypressAccount (cognitive 19) · ×1

EnvOverviewSectionComponent.keypressAccount (cognitive 19) core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:779 — EnvOverviewSectionComponent.keypressAccount has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (EnvOverviewSectionComponent.keypressRegion) 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.

D2 · Cognitive Complexity · EnvOverviewSectionComponent.keypressRegion (cognitive 19) · ×1

EnvOverviewSectionComponent.keypressRegion (cognitive 19) core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:823 — EnvOverviewSectionComponent.keypressRegion has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (EnvOverviewSectionComponent.keypressAccount) 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.

D2 · Cognitive Complexity · ServiceAccessControlComponent.keypress (cognitive 19) · ×1

ServiceAccessControlComponent.keypress (cognitive 19) core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts:451 — ServiceAccessControlComponent.keypress has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ServiceOverviewComponent.keypressAccount (cognitive 19) · ×1

ServiceOverviewComponent.keypressAccount (cognitive 19) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1453 — ServiceOverviewComponent.keypressAccount has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ServiceOverviewComponent.keypressRegion) 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.

D2 · Cognitive Complexity · ServiceOverviewComponent.keypressRegion (cognitive 19) · ×1

ServiceOverviewComponent.keypressRegion (cognitive 19) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1500 — ServiceOverviewComponent.keypressRegion has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ServiceOverviewComponent.keypressAccount) 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.

D2 · Cognitive Complexity · CreateServiceComponent.keypress (cognitive 19) · ×1

CreateServiceComponent.keypress (cognitive 19) REDACTED:1030 — CreateServiceComponent.keypress has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · addMemberToChannel (cognitive 19) · ×1

addMemberToChannel (cognitive 19) core/jazz_slack-channel/index.js:346 — addMemberToChannel has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 3 (6 pts), loops 2 (3 pts) (nesting depth added 9). None of this is in the body itself: all 19 points belong to 9 function literals inside it that branch (lines 354, 371, 376, …). 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 · getCommonData (cognitive 19) · ×1

getCommonData (cognitive 19) REDACTED:128 — getCommonData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 5, boolean chains 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 144, 131, 134, …). 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 · getScmDetails (cognitive 19) · ×1

getScmDetails (cognitive 19) core/jazz_scm-webhook/index.js:73 — getScmDetails has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 5 (6 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 19 points belong to 5 function literals inside it that branch (lines 75, 86, 95, …). 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 · utils.formatEnvironment (cognitive 18) · ×1

utils.formatEnvironment (cognitive 18) core/jazz_environments/components/utils.js:67 — utils.formatEnvironment has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (parseValue, 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 · FiltersComponent.onClick (cognitive 18) · ×1

FiltersComponent.onClick (cognitive 18) core/jazz_ui/src/app/secondary-components/filters/filters.component.ts:20 — FiltersComponent.onClick has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (5 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 · CreateServiceComponent.generateExpression (cognitive 18) · ×1

CreateServiceComponent.generateExpression (cognitive 18) REDACTED:1258 — CreateServiceComponent.generateExpression has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4 (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 · updateDeployments (cognitive 18) · ×1

updateDeployments (cognitive 18) core/jazz_deployments-event-handler/index.js:212 — updateDeployments has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). None of this is in the body itself: all 18 points belong to 4 function literals inside it that branch (lines 213, 225, 234, …). 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 · handler (cognitive 18) · ×1

handler (cognitive 18) core/jazz_events/index.js:30 — handler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 3 (5 pts), boolean chains 3 (nesting depth added 6). Of this number, 9 points are the body's own statements and 9 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 · JsonEditor.editJsonList (cognitive 17) · ×1

JsonEditor.editJsonList (cognitive 17) core/jazz_admin/components/json-editor.js:59 — JsonEditor.editJsonList has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (17 pts) (nesting depth added 10). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 68). 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 · index.getResponse (cognitive 17) · ×1

index.getResponse (cognitive 17) core/jazz_is-slack-channel-available/index.js:118 — index.getResponse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 1 (3 pts) (nesting depth added 8). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 127). 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 · LoginComponent.resetPassword (cognitive 17) · ×1

LoginComponent.resetPassword (cognitive 17) REDACTED:245 — LoginComponent.resetPassword has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 2 (4 pts), boolean chains 3 (nesting depth added 6). Of this number, 11 points are the body's own statements and 6 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 · EnvLogsSectionComponent.setAssetName (cognitive 17) · ×1

EnvLogsSectionComponent.setAssetName (cognitive 17) core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:268 — EnvLogsSectionComponent.setAssetName has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 292, 275, 282, …). 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 · ServiceLogsComponent.setAssetName (cognitive 17) · ×1

ServiceLogsComponent.setAssetName (cognitive 17) REDACTED:319 — ServiceLogsComponent.setAssetName has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 342, 326, 333, …). 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 · CronParser.validateCronExpression (cognitive 17) · ×1

CronParser.validateCronExpression (cognitive 17) core/jazz_create-serverless-service/components/cron-parser.js:84 — CronParser.validateCronExpression has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · createRule (cognitive 17) · ×1

createRule (cognitive 17) core/jazz_acl/components/utils/util.js:17 — createRule has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 3 (4 pts), boolean chains 3, loops 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 1 belongs to 10 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.formatData (cognitive 16) · ×1

utils.formatData (cognitive 16) core/jazz_admin/components/utils.js:43 — utils.formatData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, error handling 2 (4 pts), loops 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (parseValue, a function literal at line 85). 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 · index.buildSource (cognitive 16) · ×1

index.buildSource (cognitive 16) core/jazz_cloud-logs-streamer/index.js:204 — index.buildSource has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 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 · index.getUpdateServiceStatus (cognitive 16) · ×1

index.getUpdateServiceStatus (cognitive 16) core/jazz_services-handler/index.js:242 — index.getUpdateServiceStatus has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4 (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 · JenkinsStatusComponent.makeRequest (cognitive 16) · ×1

JenkinsStatusComponent.makeRequest (cognitive 16) core/jazz_ui/src/app/pages/jenkins-status/jenkins-status.component.ts:116 — JenkinsStatusComponent.makeRequest has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 6. None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 120). 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 · ServiceAccessControlComponent.onSelectionChange (cognitive 16) · ×1

ServiceAccessControlComponent.onSelectionChange (cognitive 16) core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts:262 — ServiceAccessControlComponent.onSelectionChange has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2 (nesting depth added 6). 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, split the body into named stages: move each independent 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 · CreateServiceComponent.changePlatformType (cognitive 16) · ×1

CreateServiceComponent.changePlatformType (cognitive 16) REDACTED:409 — CreateServiceComponent.changePlatformType has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2 (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 · getCodeqReport (cognitive 16) · ×1

getCodeqReport (cognitive 16) core/jazz_codeq/utils.js:208 — getCodeqReport has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (5 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 230, 209, 235, …). 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.

D22 · Internal API Consistency · Redundant type definition · ×1

Redundant type definition: SlimScrollOptions is a concrete class that duplicates all properties of the interface ISlimScrollOptions and accepts it in its constructor. This creates unnecessary coupling and maintenance overhead without adding distinct behavior or value. — Remove the SlimScrollOptions class and use ISlimScrollOptions directly as the configuration type. If a default instance is needed, provide a factory function or default values in the component/module rather than a duplicate class. (signatures: ISlimScrollOptions | SlimScrollOptions)

D32 · Data Compliance (PII/GDPR) · REDACTED · ×1

REDACTED

D32 · Data Compliance (PII/GDPR) · REDACTED · ×1

REDACTED

D35 · Change Coupling · Change-coupling hub · ×1

Change-coupling hub: service-metrics.component.ts → env-logs-section.component.ts, advanced-filters.component.ts, filter-modal.component.ts, metrics-carousel.component.ts core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts — `core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts` changes together with 4 other files — `core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts`, `core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts`, `core/jazz_ui/src/app/secondary-components/filter-modal/filter-modal.component.ts`, `core/jazz_ui/src/app/secondary-components/metrics-carousel/metrics-carousel.component.ts` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.

D36 · Supply-chain Provenance & Signing REDACTED · ×1

REDACTED

D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1

Duplicated block (9–10 lines × 2) templates/sls-app-template-java/src/main/java/com/slf/services/functions/function1/Function1.java:62 — templates/sls-app-template-java/src/main/java/com/slf/services/functions/function1/Function1.java:62-71 | templates/sls-app-template-java/src/main/java/com/slf/services/functions/function2/Function2.java:43-51 — `templates/sls-app-template-java/src/main/java/com/slf/services/functions/function1/Function1.java` and `templates/sls-app-template-java/src/main/java/com/slf/services/functions/function2/Function2.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 10 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `templates/sls-app-template-java/src/main/java/com/slf/services/functions/function1/Function1.java:62` 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. 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 (19 lines × 2) · ×1

Duplicated block (19 lines × 2) templates/api-template-java/src/main/java/com/slf/exceptions/BaseException.java:12 — templates/api-template-java/src/main/java/com/slf/exceptions/BaseException.java:12-30 | templates/function-template-java/src/main/java/com/slf/exceptions/BaseException.java:12-30 — 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.

D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1

Duplicated block (27 lines × 3) templates/api-template-java/src/main/java/com/slf/model/ErrorInfo.java:10 — templates/api-template-java/src/main/java/com/slf/model/ErrorInfo.java:10-36 | templates/function-template-java/src/main/java/com/slf/model/ErrorInfo.java:10-36 | templates/sls-app-template-java/src/main/java/com/slf/model/ErrorInfo.java:8-34 — before extracting anything, compare `templates/api-template-java/src/main/java/com/slf/model/ErrorInfo.java` and `templates/function-template-java/src/main/java/com/slf/model/ErrorInfo.java` 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 (23 lines × 3) · ×1

Duplicated block (23 lines × 3) templates/api-template-java/src/main/java/com/slf/model/Response.java:10 — templates/api-template-java/src/main/java/com/slf/model/Response.java:10-32 | templates/function-template-java/src/main/java/com/slf/model/Response.java:9-31 | templates/sls-app-template-java/src/main/java/com/slf/model/Response.java:9-31 — before extracting anything, compare `templates/function-template-java/src/main/java/com/slf/model/Response.java` and `templates/sls-app-template-java/src/main/java/com/slf/model/Response.java` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `input` to `Map` in one and `Object` 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.

D4 · Code Duplication · Duplicated block (26 lines × 3) · ×1

Duplicated block (26 lines × 3) templates/api-template-python/components/logger.py:24 — templates/api-template-python/components/logger.py:24-49 | templates/function-template-python/components/logger.py:37-62 | templates/sls-app-template-python/components/logger.py:24-49 — before extracting anything, compare `templates/api-template-python/components/logger.py` and `templates/function-template-python/components/logger.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 92 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 (21 lines × 3) · ×1

Duplicated block (21 lines × 3) templates/api-template-python/components/logger.py:114 — templates/api-template-python/components/logger.py:114-134 | templates/function-template-python/components/logger.py:127-147 | templates/sls-app-template-python/components/logger.py:114-134 — before extracting anything, compare `templates/api-template-python/components/logger.py` and `templates/function-template-python/components/logger.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 92 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 (20 lines × 3) · ×1

Duplicated block (20 lines × 3) templates/api-template-python/components/logger.py:68 — templates/api-template-python/components/logger.py:68-87 | templates/function-template-python/components/logger.py:81-100 | templates/sls-app-template-python/components/logger.py:68-87 — before extracting anything, compare `templates/api-template-python/components/logger.py` and `templates/function-template-python/components/logger.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 92 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 (8 lines × 3) · ×1

Duplicated block (8 lines × 3) templates/api-template-python/components/logger.py:55 — templates/api-template-python/components/logger.py:55-62 | templates/function-template-python/components/logger.py:68-75 | templates/sls-app-template-python/components/logger.py:55-62 — before extracting anything, compare `templates/api-template-python/components/logger.py` and `templates/function-template-python/components/logger.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 92 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 (21 lines × 2) · ×1

Duplicated block (21 lines × 2) templates/api-template-python/components/errors.py:9 — templates/api-template-python/components/errors.py:9-29 | templates/sls-app-template-python/components/errors.py:9-29 — before extracting anything, compare `templates/api-template-python/components/errors.py` and `templates/sls-app-template-python/components/errors.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 (6 lines × 2) · ×1

Duplicated block (6 lines × 2) templates/api-template-python/components/config.py:31 — templates/api-template-python/components/config.py:31-36 | templates/function-template-python/components/config.py:31-36 — 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 `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 × 2) · ×1

Duplicated block (20 lines × 2) templates/sls-app-template-python/functions/function1/index.py:17 — templates/sls-app-template-python/functions/function1/index.py:17-36 | templates/sls-app-template-python/functions/function2/index.py:17-36 — `templates/sls-app-template-python/functions/function1/index.py` and `templates/sls-app-template-python/functions/function2/index.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 20 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `templates/sls-app-template-python/functions/function1/index.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. 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 lines × 2) · ×1

Duplicated block (24 lines × 2) templates/api-template-go/logger.go:92 — templates/api-template-go/logger.go:92-115 | templates/function-template-go/logger.go:92-115 — `templates/api-template-go/logger.go` and `templates/function-template-go/logger.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1

Duplicated block (22 lines × 2) templates/api-template-go/config.go:30 — templates/api-template-go/config.go:30-51 | templates/function-template-go/config.go:30-51 — `templates/api-template-go/config.go` and `templates/function-template-go/config.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `templates/api-template-go/config.go:30` 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 (17 lines × 2) · ×1

Duplicated block (17 lines × 2) templates/sls-app-template-go/functions/function1/main.go:42 — templates/sls-app-template-go/functions/function1/main.go:42-58 | templates/sls-app-template-go/functions/function2/main.go:42-58 — `templates/sls-app-template-go/functions/function1/main.go` and `templates/sls-app-template-go/functions/function2/main.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 17 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `templates/sls-app-template-go/functions/function1/main.go:42` 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 (13 lines × 3) · ×1

Duplicated block (13 lines × 3) templates/api-template-go/config.go:26 — templates/api-template-go/config.go:26-38 | templates/function-template-go/config.go:26-38 | templates/sls-app-template-go/components/config.go:28-40 — `templates/api-template-go/config.go` and `templates/function-template-go/config.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `templates/api-template-go/config.go:26` 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 (72 lines × 3) · ×1

Duplicated block (72 lines × 3) templates/api-template-go/error-handler.go:12 — templates/api-template-go/error-handler.go:12-83 | templates/function-template-go/error-handler.go:12-83 | templates/sls-app-template-go/components/error-handler.go:12-83 — `templates/api-template-go/error-handler.go` and `templates/function-template-go/error-handler.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 72 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1

Duplicated block (10 lines × 3) templates/api-template-go/logger.go:118 — templates/api-template-go/logger.go:118-127 | templates/function-template-go/logger.go:118-127 | templates/sls-app-template-go/components/logger.go:123-132 — `templates/api-template-go/logger.go` and `templates/function-template-go/logger.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

D43 · Malicious Dependencies · Malicious package · ×1

REDACTED

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — .NET suite — Coverage NOT MEASURED: the .NET half could not be measured — the repository wires up no coverage collector for `--collect:"XPlat Code Coverage"` to use; the JavaScript/TypeScript half measured 76.7% (mocha in core/jazz_acl/: not run; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_admin/; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_apigee-proxy-aws/; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_asset-event-handler/; mocha in core/jazz_assets/: not run; mocha in core/jazz_cloud-logs-streamer/: not run; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_codeq/; mocha in core/jazz_cognito-admin-authorizer/: not run; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_cognito-authorizer/; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_create-serverless-service/; mocha + nyc via `npm install --ignore-scripts` (no lockfile) in core/jazz_delete-serverless-service/; mocha in core/jazz_deployments/: not run). This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.

IC1 · Incompleteness & stubs · Fake-async · ×1

Fake-async — async method never awaits builds/jazz_azure-create-service/components/CommandMapping.js:18 — `instantiate` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

R1 · Type Safety · Type Safety · ×1

Type Safety — 203 typed · 379 plain JS — the untyped files are builds/azure-config-pack/nodejs/index.js, builds/jazz-build-module/apigee/templates/coreAPI_default/Common/resources/jsc/cf_CORS.js, builds/jazz-build-module/apigee/templates/coreAPI_secure/Common/resources/jsc/cf_CORS.js, builds/jazz_azure-create-service/components/ApiApp.js, builds/jazz_azure-create-service/components/ClientFactory.js, builds/jazz_azure-create-service/components/CommandMapping.js (+373 more).

R10 · Code Duplication · Forked directory tree (10 identical files, ~10068 lines × 2 trees) · ×1

Forked directory tree (10 identical files, ~10068 lines × 2 trees) core/jazz-web/css/bootstrap.css:1 — core/jazz-web/ and templates/static-website-template/app/ are near-verbatim copies of each other: 10 files are byte-identical under the same relative paths (~10068 lines; the trees hold 12 and 11 files). That is one structural fact, not 10 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 · Forked directory tree (45 identical files, ~517 lines × 2 trees) · ×1

Forked directory tree (45 identical files, ~517 lines × 2 trees) builds/jazz-build-module/apigee/templates/coreAPI_default/Proxy/proxies/ProxyEndpoint.xml.ftl:1 — builds/jazz-build-module/apigee/templates/coreAPI_default/ and builds/jazz-build-module/apigee/templates/coreAPI_secure/ are near-verbatim copies of each other: 45 files are byte-identical under the same relative paths (~517 lines; the trees hold 47 and 47 files). That is one structural fact, not 45 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.

R10 · Code Duplication · Duplication concentrated across 35 sibling directories (130 clone groups) · ×1

Duplication concentrated across 35 sibling directories (130 clone groups) core/jazz_deployments/index.js:37 — 130 duplicated blocks under core/ have copies in at least two of the sibling directories jazz_acl, jazz_admin, jazz_apigee-proxy-aws, jazz_asset-event-handler, jazz_assets, jazz_cloud-logs-streamer (+29 more sibling(s) not listed) — 99 of them are reported below, and 31 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 130 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 130 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 130 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 (41 clone groups) · ×1

Duplication concentrated across 13 sibling directories (41 clone groups) core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:365 — 41 duplicated blocks under core/jazz_ui/src/app/pages/ have copies in at least two of the sibling directories environment-assets, environment-codequality, environment-deployment, environment-detail, environment-logs, environment-overview (+7 more sibling(s) not listed) — 33 of them are reported below, and 8 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 41 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 41 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 41 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 3 sibling directories (25 clone groups) · ×1

Duplication concentrated across 3 sibling directories (25 clone groups) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:882 — 25 duplicated blocks under core/jazz_ui/src/app/ have copies in at least two of the sibling directories pages, primary-components, secondary-components — 21 of them are reported below, and 4 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 25 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 25 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 25 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 (6 clone groups) · ×1

Duplication concentrated across 2 sibling directories (6 clone groups) core/jazz_acl/components/logger.js:16 — 6 of the duplicated blocks reported below have copies in at least two of the sibling directories core, templates under the repository root. That concentration is one structural fact, not 6 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 6 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 · Duplicated block with local edits (135 matched lines × 2 locations) · ×1

Duplicated block with local edits (135 matched lines × 2 locations) core/jazz_deployments/index.js:37 — core/jazz_deployments/index.js:37 · core/jazz_environments/index.js:34 — the two spans are one implementation copied and then locally edited — 626 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 with local edits (122 matched lines × 2 locations) · ×1

Duplicated block with local edits (122 matched lines × 2 locations) REDACTED:29 — REDACTED:29 · core/jazz_token-authorizer/index.js:29 — the two spans are one implementation copied and then locally edited — 786 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 (118 lines × 2 locations) · ×1

Duplicated block (118 lines × 2 locations) core/jazz_cognito-authorizer/components/auth-policy.js:37 — core/jazz_cognito-authorizer/components/auth-policy.js:37 · core/jazz_token-authorizer/index.js:200 — 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 (113 lines × 2 locations) · ×1

Duplicated block (113 lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:882 — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:882 · core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts:252 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (107 lines × 2 locations) · ×1

Duplicated block (107 lines × 2 locations) core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:365 — core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:365 · core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:502 — 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 (95 matched lines × 2 locations) · ×1

Duplicated block with local edits (95 matched lines × 2 locations) core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts:90 — core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts:90 · core/jazz_ui/src/app/secondary-components/advanced-filters/internal/advanced-filters.component.ts:67 — the two spans are one implementation copied and then locally edited — 597 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 (93 identical lines × 2 files) · ×1

Wholesale file copy (93 identical lines × 2 files) core/jazz_create-serverless-service/components/validate-sls-yml.js:17 — core/jazz_create-serverless-service/components/validate-sls-yml.js:17 · core/jazz_environments/components/validate-sls-yml.js:17 — these 2 files are line-for-line copies of one another — 93 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 (87 matched lines × 2 locations) · ×1

Duplicated block with local edits (87 matched lines × 2 locations) core/jazz_ui/src/app/secondary-components/filter-metrics/filter-metrics.component.ts:23 — core/jazz_ui/src/app/secondary-components/filter-metrics/filter-metrics.component.ts:23 · core/jazz_ui/src/app/secondary-components/filter-modal/filter-modal.component.ts:74 — the two spans are one implementation copied and then locally edited — 519 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 with local edits (80 matched lines × 2 locations) · ×1

Duplicated block with local edits (80 matched lines × 2 locations) core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:631 — core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:631 · core/jazz_ui/src/app/secondary-components/table-template/table-template.component.ts:184 — the two spans are one implementation copied and then locally edited — 488 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 with local edits (79 matched lines × 2 locations) · ×1

Duplicated block with local edits (79 matched lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1026 — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1026 · core/jazz_ui/src/app/secondary-components/table-template/table-template.component.ts:184 — the two spans are one implementation copied and then locally edited — 488 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 (76 lines × 2 locations) · ×1

Duplicated block (76 lines × 2 locations) core/jazz_asset-event-handler/index.js:73 — core/jazz_asset-event-handler/index.js:73 · core/jazz_environment-event-handler/index.js:75 — 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 (75 lines × 2 locations) · ×1

Duplicated block (75 lines × 2 locations) REDACTED:368 — REDACTED:368 · REDACTED:241 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (74 matched lines × 2 locations) · ×1

Duplicated block with local edits (74 matched lines × 2 locations) core/jazz_deployments-event-handler/index.js:40 — core/jazz_deployments-event-handler/index.js:40 · core/jazz_environment-event-handler/index.js:38 — the two spans are one implementation copied and then locally edited — 533 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 (71 lines × 2 locations) · ×1

Duplicated block (71 lines × 2 locations) core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:236 — core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:236 · REDACTED:287 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (61 matched lines × 2 locations) · ×1

Duplicated block with local edits (61 matched lines × 2 locations) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:288 — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:288 · REDACTED:1238 — the two spans are one implementation copied and then locally edited — 398 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 (61 identical lines × 2 files) · ×1

Wholesale file copy (61 identical lines × 2 files) core/jazz_ui/src/app/primary-components/checkbox-group-region/checkbox-group-region.component.ts:7 — core/jazz_ui/src/app/primary-components/checkbox-group-region/checkbox-group-region.component.ts:7 · core/jazz_ui/src/app/primary-components/checkbox-group/checkbox-group.component.ts:7 — 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.

R10 · Code Duplication · Duplicated block with local edits (59 matched lines × 2 locations) · ×1

Duplicated block with local edits (59 matched lines × 2 locations) core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:680 — core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:680 · core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1379 — the two spans are one implementation copied and then locally edited — 336 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 (56 lines × 39 locations) · ×1

Duplicated block (56 lines × 39 locations) core/jazz_acl/components/logger.js:16 — core/jazz_acl/components/logger.js:16 · core/jazz_admin/components/logger.js:16 · core/jazz_apigee-proxy-aws/components/logger.js:16 · core/jazz_asset-event-handler/components/logger.js:16 · +35 more site(s) not listed — the 39 copies are spread across 39 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. There is one copy in each of 39 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.

R10 · Code Duplication · Duplicated block (54 lines × 2 locations) · ×1

Duplicated block (54 lines × 2 locations) core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.ts:271 — core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.ts:271 · core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:430 — 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 (45 lines × 2 locations) · ×1

Duplicated block (45 lines × 2 locations) core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:458 — core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:458 · REDACTED:660 — 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 (43 lines × 2 locations) · ×1

Duplicated block (43 lines × 2 locations) REDACTED:33 — REDACTED:33 · REDACTED:33 — 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 (41 lines × 2 locations) · ×1

Duplicated block (41 lines × 2 locations) core/jazz_asset-event-handler/index.js:339 — core/jazz_asset-event-handler/index.js:339 · core/jazz_environment-event-handler/index.js:606 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (40 matched lines × 2 locations) · ×1

Duplicated block with local edits (40 matched lines × 2 locations) core/jazz_acl/components/scm/bitbucket.js:72 — core/jazz_acl/components/scm/bitbucket.js:72 · core/jazz_acl/components/scm/gitlab.js:131 — the two spans are one implementation copied and then locally edited — 285 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 (40 lines × 5 locations) · ×1

Duplicated block (40 lines × 5 locations) core/jazz_email/components/error-handler.js:24 — core/jazz_email/components/error-handler.js:24 · core/jazz_is-service-available/components/error-handler.js:24 · core/jazz_login/components/error-handler.js:24 · core/jazz_token-authorizer/components/error-handler.js:25 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block (40 lines × 3 locations) · ×1

Duplicated block (40 lines × 3 locations) core/jazz_environment-event-handler/components/error-handler.js:17 — core/jazz_environment-event-handler/components/error-handler.js:17 · core/jazz_events-handler/components/error-handler.js:8 · core/jazz_services-handler/components/error-handler.js:24 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block (38 lines × 2 locations) · ×1

Duplicated block (38 lines × 2 locations) core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:539 — core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:539 · core/jazz_ui/src/app/pages/services-list/services-list.component.ts:266 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) · ×1

Duplicated block with local edits (38 matched lines × 2 locations) core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts:19 — core/jazz_ui/src/app/secondary-components/advanced-filters/OSS/advanced-filters.component.ts:19 · core/jazz_ui/src/app/secondary-components/advanced-filters/internal/advanced-filters.component.ts:15 — the two spans are one implementation copied and then locally edited — 355 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 with local edits (36 matched lines × 2 locations) · ×1

Duplicated block with local edits (36 matched lines × 2 locations) core/jazz_ui/src/app/pages/services-list/services-list.component.ts:338 — core/jazz_ui/src/app/pages/services-list/services-list.component.ts:338 · core/jazz_ui/src/app/pages/services-list/services-list.component.ts:483 — the two spans are one implementation copied and then locally edited — 269 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 (35 lines × 7 locations) · ×1

Duplicated block (35 lines × 7 locations) core/jazz_admin/components/error-handler.js:9 — core/jazz_admin/components/error-handler.js:9 · core/jazz_delete-serverless-service/components/error-handler.js:25 · core/jazz_environments/components/error-handler.js:25 · core/jazz_logout/components/error-handler.js:25 · +3 more site(s) not listed — the 7 copies are spread across 7 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block (35 lines × 3 locations) · ×1

Duplicated block (35 lines × 3 locations) core/jazz_asset-event-handler/components/error-handler.js:17 — core/jazz_asset-event-handler/components/error-handler.js:17 · core/jazz_deployments-event-handler/components/error-handler.js:8 · core/jazz_slack-event-handler/components/error-handler.js:25 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 49, cognitive 106) · ×1

Complex function (anonymous) (cyclomatic 49, cognitive 106) core/jazz_create-serverless-service/index.js:317 — (anonymous) has cyclomatic complexity 49 and cognitive complexity 106; 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 handler (cyclomatic 49, cognitive 49) · ×1

Complex function handler (cyclomatic 49, cognitive 49) core/jazz_t-vault/index.js:37 — handler has cyclomatic complexity 49 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 handler (cyclomatic 47, cognitive 73) · ×1

Complex function handler (cyclomatic 47, cognitive 73) core/jazz_create-serverless-service/index.js:38 — handler has cyclomatic complexity 47 and cognitive complexity 73; 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 createService (cyclomatic 38, cognitive 57) · ×1

Complex function createService (cyclomatic 38, cognitive 57) REDACTED:667 — createService has cyclomatic complexity 38 and cognitive complexity 57; 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 getNotificationMessage (cyclomatic 32, cognitive 60) · ×1

Complex function getNotificationMessage (cyclomatic 32, cognitive 60) core/jazz_slack-event-handler/components/utils.js:19 — getNotificationMessage 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 applyFilter (cyclomatic 32, cognitive 38) · ×1

Complex function applyFilter (cyclomatic 32, cognitive 38) core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:416 — applyFilter has cyclomatic complexity 32 and cognitive complexity 38; 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 disableForm (cyclomatic 32, cognitive 31) · ×1

Complex function disableForm (cyclomatic 32, cognitive 31) REDACTED:977 — disableForm has cyclomatic complexity 32 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 29, cognitive 22) · ×1

Complex function (anonymous) (cyclomatic 29, cognitive 22) core/jazz_environments/index.js:171 — (anonymous) has cyclomatic complexity 29 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 check_empty_fields (cyclomatic 28, cognitive 32) · ×1

Complex function check_empty_fields (cyclomatic 28, cognitive 32) core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:758 — check_empty_fields has cyclomatic complexity 28 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function handler (cyclomatic 26, cognitive 48) · ×1

Complex function handler (cyclomatic 26, cognitive 48) core/jazz_logs/index.js:34 — handler has cyclomatic complexity 26 and cognitive complexity 48; 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 processACLRequest (cyclomatic 25, cognitive 39) · ×1

Complex function processACLRequest (cyclomatic 25, cognitive 39) core/jazz_acl/index.js:55 — processACLRequest has cyclomatic complexity 25 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function handler (cyclomatic 25, cognitive 30) · ×1

Complex function handler (cyclomatic 25, cognitive 30) core/jazz_usermanagement/index.js:36 — handler has cyclomatic complexity 25 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 25, cognitive 21) · ×1

Complex function (anonymous) (cyclomatic 25, cognitive 21) core/jazz_scm-webhook/index.js:131 — (anonymous) has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function handler (cyclomatic 24, cognitive 26) · ×1

Complex function handler (cyclomatic 24, cognitive 26) core/jazz_services/index.js:34 — handler has cyclomatic complexity 24 and cognitive complexity 26; 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 getServiceData (cyclomatic 23, cognitive 26) · ×1

Complex function getServiceData (cyclomatic 23, cognitive 26) core/jazz_create-serverless-service/components/crud/create.js:40 — getServiceData has cyclomatic complexity 23 and cognitive complexity 26; 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 DatePickerOptions (cyclomatic 23, cognitive 22) · ×1

Complex function DatePickerOptions (cyclomatic 23, cognitive 22) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:16 — DatePickerOptions has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function SlimScrollOptions (cyclomatic 23, cognitive 22) · ×1

Complex function SlimScrollOptions (cyclomatic 23, cognitive 22) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/classes/slimscroll-options.class.js:2 — SlimScrollOptions has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function constructor (cyclomatic 23, cognitive 22) · ×1

Complex function constructor (cyclomatic 23, cognitive 22) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/classes/slimscroll-options.class.ts:28 — constructor has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function generateCalendar (cyclomatic 22, cognitive 45) · ×1

Complex function generateCalendar (cyclomatic 22, cognitive 45) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js:158 — generateCalendar has cyclomatic complexity 22 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 22, cognitive 32) · ×1

Complex function (anonymous) (cyclomatic 22, cognitive 32) core/jazz_environments/index.js:47 — (anonymous) has cyclomatic complexity 22 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R3 · Large Files · core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts · ×1

core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts: 1376 lines of code core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1 — core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts has 1376 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: 1172 lines of code REDACTED:1 — REDACTED has 1172 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: 824 lines of code REDACTED:1 — REDACTED has 824 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 · core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts · ×1

core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts: 796 lines of code core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:1 — core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts has 796 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 · core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts · ×1

core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts: 774 lines of code core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:1 — core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts has 774 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 · core/jazz_metrics/index.js · ×1

core/jazz_metrics/index.js: 730 lines of code core/jazz_metrics/index.js:1 — core/jazz_metrics/index.js has 730 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 · core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts · ×1

core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts: 717 lines of code core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:1 — core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts has 717 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 · core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts · ×1

core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts: 710 lines of code core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:1 — core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts has 710 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 · core/jazz_ui/src/app/pages/services-list/services-list.component.ts · ×1

core/jazz_ui/src/app/pages/services-list/services-list.component.ts: 676 lines of code core/jazz_ui/src/app/pages/services-list/services-list.component.ts:1 — core/jazz_ui/src/app/pages/services-list/services-list.component.ts has 676 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 · core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts · ×1

core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts: 599 lines of code core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:1 — core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts has 599 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 · core/jazz_environment-event-handler/index.js · ×1

core/jazz_environment-event-handler/index.js: 595 lines of code core/jazz_environment-event-handler/index.js:1 — core/jazz_environment-event-handler/index.js has 595 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 · core/jazz_t-vault/components/utils/vault.js · ×1

core/jazz_t-vault/components/utils/vault.js: 555 lines of code core/jazz_t-vault/components/utils/vault.js:1 — core/jazz_t-vault/components/utils/vault.js has 555 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 · core/jazz_deployments/index.js · ×1

core/jazz_deployments/index.js: 552 lines of code core/jazz_deployments/index.js:1 — core/jazz_deployments/index.js has 552 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 · core/jazz_create-serverless-service/index.js · ×1

core/jazz_create-serverless-service/index.js: 518 lines of code core/jazz_create-serverless-service/index.js:1 — core/jazz_create-serverless-service/index.js has 518 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 · core/jazz_slack-channel/index.js · ×1

core/jazz_slack-channel/index.js: 504 lines of code core/jazz_slack-channel/index.js:1 — core/jazz_slack-channel/index.js has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · REDACTED · ×1

REDACTED: 502 lines of code REDACTED:1 — REDACTED has 502 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: 459 lines of code REDACTED:1 — REDACTED has 459 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 · core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts · ×1

core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts: 455 lines of code core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts:1 — core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts has 455 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: 453 lines of code REDACTED:1 — REDACTED has 453 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 · core/jazz_token-authorizer/index.js · ×1

core/jazz_token-authorizer/index.js: 444 lines of code core/jazz_token-authorizer/index.js:1 — core/jazz_token-authorizer/index.js has 444 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 · core/jazz_usermanagement/index.js · ×1

core/jazz_usermanagement/index.js: 437 lines of code core/jazz_usermanagement/index.js:1 — core/jazz_usermanagement/index.js has 437 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: 424 lines of code REDACTED:1 — REDACTED has 424 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 · core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts · ×1

core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts: 414 lines of code core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts:1 — core/jazz_ui/src/app/secondary-components/service-overview-multienv/service-overview-multienv.component.ts has 414 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 · core/jazz_metrics/components/utils.js · ×1

core/jazz_metrics/components/utils.js: 405 lines of code core/jazz_metrics/components/utils.js:1 — core/jazz_metrics/components/utils.js has 405 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 · core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts · ×1

core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts: 402 lines of code core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts:1 — core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R6 · Tooling · No typecheck script · ×1

No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

R7 · Dead Code · Dead file (~1304 LoC) · ×1

Dead file (~1304 LoC) REDACTED — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (core/jazz_ui/src/app/service-module/service.module.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~223 LoC) · ×1

Dead file (~223 LoC) core/jazz_ui/src/app/primary-components/daterange-picker/ng2-slimscroll/src/directives/slimscroll.directive.js — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~164 LoC) · ×1

Dead file (~164 LoC) core/jazz_ui/src/app/pages/service-metrics/data.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~129 LoC) · ×1

Dead file (~129 LoC) core/jazz_ui/src/app/pages/admin-dashboard/admin-dashboard.component.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (core/jazz_ui/src/app/admin-module/admin.module.ts, core/jazz_ui/src/app/admin-module/admin.route.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~82 LoC) · ×1

Dead file (~82 LoC) core/jazz_ui/src/app/primary-components/json-viewer/json-viewer.component.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (core/jazz_ui/src/app/admin-module/admin.module.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~76 LoC) · ×1

Dead file (~76 LoC) core/jazz_ui/src/app/service-module/service.module.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~48 LoC) · ×1

Dead file (~48 LoC) core/jazz_events-handler/components/error-handler.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~47 LoC) · ×1

Dead file (~47 LoC) core/jazz_cloud-logs-streamer/components/error-handler.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~34 LoC) · ×1

Dead file (~34 LoC) core/jazz_ui/src/test.ts — no import path from any entry point (53 application, 26 tooling, 114 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 (~30 LoC) · ×1

Dead file (~30 LoC) core/jazz_ui/src/app/core/services/admin-utils.service.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (core/jazz_ui/src/app/admin-module/admin.module.ts, core/jazz_ui/src/app/pages/admin-dashboard/admin-dashboard.component.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~24 LoC) · ×1

Dead file (~24 LoC) core/jazz_acl/components/response.js — no import path from any entry point (53 application, 26 tooling, 114 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 (~23 LoC) · ×1

Dead file (~23 LoC) core/jazz_ui/src/app/admin-module/admin.route.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (core/jazz_ui/src/app/admin-module/admin.module.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~21 LoC) · ×1

Dead file (~21 LoC) core/jazz_ui/src/app/pages/admin/admin.component.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (core/jazz_ui/src/app/admin-module/admin.module.ts, core/jazz_ui/src/app/admin-module/admin.route.ts, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~20 LoC) · ×1

Dead file (~20 LoC) templates/angular-website-template/app/src/test.ts — no import path from any entry point (53 application, 26 tooling, 114 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 (~12 LoC) · ×1

Dead file (~12 LoC) core/jazz_ui/src/app/service-module/service.module.declarations.common.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~11 LoC) · ×1

Dead file (~11 LoC) core/jazz_ui/src/config/templates/java-yaml.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (REDACTED, core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~10 LoC) · ×1

Dead file (~10 LoC) core/jazz_ui/src/app/oss/oss.module.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~1 LoC) · ×1

Dead file (~1 LoC) core/jazz_ui/src/app/service-module/service.module.imports.internal.ts — no import path from any entry point (53 application, 26 tooling, 114 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (core/jazz_ui/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R8 · Dependency Hygiene · Unused dependency 'axios' · ×1

Unused dependency 'axios' — Declared in builds/jazz_azure-create-service/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.

R8 · Dependency Hygiene · Unused dependency 'escape-json-node' · ×1

Unused dependency 'escape-json-node' — Declared in builds/jazz_azure-create-service/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.

R8 · Dependency Hygiene · Unused dependency 'form-data' · ×1

Unused dependency 'form-data' — Declared in builds/jazz_azure-create-service/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 core/jazz_ui/src/index.html:9 — `https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.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. 2 such include(s) across the repository's markup.

SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1

NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.

X29 · Per-element action decided by a fixed element · Per-element action decided by a fixed element · ×1

Per-element action decided by a fixed element core/jazz_services/components/utils.js:180 — This loop runs once per element of `new_keys`, and the statement it guards acts on the element it is on — `new_keys[i]`. The test deciding whether that statement runs does not: `old_keys.indexOf(new_keys[0]) >= 0` reads `new_keys[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.

Minor — 233 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×156

Orphaned file core/jazz_metrics/index.js: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 REDACTED: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 core/jazz_ui/src/app/pages/environment-overview/env-overview-section.component.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/lib-dist/ng2-datepicker.component.js: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 core/jazz_create-serverless-service/index.js: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 core/jazz_environment-event-handler/index.js: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 core/jazz_ui/src/app/pages/service-cost/service-cost.component.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/jazz_ui/src/app/pages/environment-logs/env-logs-section.component.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/jazz_t-vault/components/utils/vault.js: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 core/jazz_ui/src/app/pages/services-list/services-list.component.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/jazz_token-authorizer/index.js: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 REDACTED: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 core/jazz_deployments/index.js: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 core/jazz_ui/src/app/pages/environment-deployment/env-deployments-section.component.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED: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 REDACTED: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 core/jazz_t-vault/index.js: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 core/jazz_slack-channel/index.js: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 REDACTED: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 core/jazz_usermanagement/index.js: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 core/jazz_ui/src/app/pages/service-access-control/service-access-control.component.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/jazz_environments/index.js: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 core/jazz_metrics/components/utils.js: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 core/jazz_cloud-logs-streamer/index.js: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 core/jazz_ui/src/app/pages/service-detail/service-detail.component.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 131 more in this group — see findings.md.

X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×40

Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/casbin.js:94 — `debug` at line 94 is called with an argument built by `JSON.stringify(result)` (line 94), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/casbin.js:111 — `debug` at line 111 is called with an argument built by `JSON.stringify(action)` (line 111), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/scm/gitlab.js:168 — `debug` at line 168 is called with an argument built by `JSON.stringify(payload)` (line 168), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/scm/gitlab.js:170 — `debug` at line 170 is called with an argument built by `JSON.stringify(response)` (line 170), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/scm/bitbucket.js:109 — `debug` at line 109 is called with an argument built by `JSON.stringify(response)` (line 109), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:48 — `debug` at line 48 is called with an argument built by `JSON.stringify(payload)` (line 48), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:52 — `debug` at line 52 is called with an argument built by `JSON.stringify(response)` (line 52), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:95 — `debug` at line 95 is called with an argument built by `JSON.stringify(result)` (line 95), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:122 — `debug` at line 122 is called with an argument built by `JSON.stringify(payload)` (line 122), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:125 — `debug` at line 125 is called with an argument built by `JSON.stringify(response)` (line 125), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:154 — `debug` at line 154 is called with an argument built by `JSON.stringify(payload)` (line 154), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:157 — `debug` at line 157 is called with an argument built by `JSON.stringify(response)` (line 157), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:194 — `debug` at line 194 is called with an argument built by `JSON.stringify(result)` (line 194), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:222 — `debug` at line 222 is called with an argument built by `JSON.stringify(result)` (line 222), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/vault.js:258 — `debug` at line 258 is called with an argument built by `JSON.stringify(result)` (line 258), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/getList.js:25 — `debug` at line 25 is called with an argument built by `JSON.stringify(dataDb)` (line 25), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/getList.js:50 — `debug` at line 50 is called with an argument built by `JSON.stringify(scanResult)` (line 50), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/getList.js:79 — `debug` at line 79 is called with an argument built by `JSON.stringify(scanparams)` (line 79), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/environment.js:33 — `debug` at line 33 is called with an argument built by `JSON.stringify(payload)` (line 33), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_acl/components/utils/environment.js:36 — `debug` at line 36 is called with an argument built by `JSON.stringify(response)` (line 36), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_apigee-proxy-aws/index.js:43 — `verbose` at line 43 is called with an argument built by `JSON.stringify(payload)` (line 43), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_apigee-proxy-aws/index.js:59 — `verbose` at line 59 is called with an argument built by `JSON.stringify(responseObj)` (line 59), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_asset-event-handler/index.js:195 — `debug` at line 195 is called with an argument built by `JSON.stringify(svcContext)` (line 195), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_asset-event-handler/index.js:216 — `debug` at line 216 is called with an argument built by `JSON.stringify(assetApiPayload)` (line 216), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted core/jazz_asset-event-handler/index.js:228 — `debug` at line 228 is called with an argument built by `JSON.stringify(svcPayload)` (line 228), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
+ 15 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×25

Duplicated predicate core/jazz-web/js/bootstrap.js:855 — `!/(38|40|27|32)/.test(e.which) || /input|textarea/i.test(e.target.tagName)` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:723 — `!data && options.toggle && /show|hide/.test(option)` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:867 — `!isActive && e.which != 27 || isActive && e.which == 27` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz_services-handler/index.js:152 — `!payload.EVENT_NAME.S || !payload.EVENT_STATUS.S` appears character-identically in 2 files — core/jazz_services-handler/index.js, core/jazz_slack-event-handler/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.
Duplicated predicate core/jazz-web/js/bootstrap.js:1430 — `!self.options.delay || !self.options.delay.hide` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1396 — `!self.options.delay || !self.options.delay.show` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1171 — `!this.bodyIsOverflowing && modalIsOverflowing` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:303 — `$(e.target).is('input[type="radio"]') || $(e.target).is('input[type="checkbox"]')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:147 — `$.support.transition && $parent.hasClass('fade')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1596 — `$.support.transition && $tip.hasClass('fade')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1003 — `$.support.transition && that.$element.hasClass('fade')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1058 — `$.support.transition && this.$element.hasClass('fade')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:455 — `$.support.transition && this.$element.hasClass('slide')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1505 — `$.support.transition && this.$tip.hasClass('fade')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1609 — `$e.attr('title') || typeof $e.attr('data-original-title') != 'string'` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:451 — `$nextIndicator && $nextIndicator.addClass('active')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1249 — `$this.attr('data-target') || (href && href.replace(/.*(?=#[^\s]+$)/, ''))` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:521 — `$this.attr('data-target') || (href = $this.attr('href')) && href.replace(/.*(?=#[^\s]+$)/, '')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:1257 — `$this.is(':visible') && $this.trigger('focus')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:707 — `$trigger.attr('data-target') || (href = $trigger.attr('href')) && href.replace(/.*(?=#[^\s]+$)/, '')` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz-web/js/bootstrap.js:829 — `'ontouchstart' in document.documentElement && !$parent.closest('.navbar-nav').length` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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:488 — `(!this.allowMethods || this.allowMethods.length === 0) && (!this.denyMethods || this.denyMethods.length === 0)` appears character-identically in 3 files — REDACTED, core/jazz_cognito-authorizer/components/auth-policy.js, core/jazz_token-authorizer/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.
Duplicated predicate core/jazz-web/js/bootstrap.js:1950 — `($href && $href.length && $href.is(':visible') && [[$href[offsetMethod]().top + offsetBase, href]]) || null` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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 core/jazz_ui/src/app/pages/landing/landing.component.ts:192 — `(direction && (val - prevVal) < 0) || (!direction && (val - prevVal) > 0)` appears character-identically in 2 files — core/jazz_ui/src/app/pages/landing/landing.component.ts, core/jazz_ui/src/app/secondary-components/jazz-header/jazz-header.component.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 core/jazz-web/js/bootstrap.js:384 — `(direction == 'prev' && activeIndex === 0) || (direction == 'next' && activeIndex == (this.$items.length - 1))` appears character-identically in 2 files — core/jazz-web/js/bootstrap.js, templates/static-website-template/app/js/bootstrap.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.

D34 · Knowledge Freshness · Most significant orphaned file · ×3

Most significant orphaned file core/jazz_ui/src/app/pages/service-overview/service-overview.component.ts:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file REDACTED:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file core/jazz_ui/src/app/pages/service-metrics/service-metrics.component.ts:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.

IC1 · Incompleteness & stubs · Empty method body · ×2

Empty method body core/jazz_ui/src/app/pages/environment-assets/env-assets-section.component.ts:268 — `errorIncluded` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body core/jazz_ui/src/app/secondary-components/create-service/focus.directive.ts:13 — `ngOnInit` has an empty body — confirm it's an intentional no-op and not an unfinished method.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D34 · Knowledge Freshness · Dormant codebase · ×1

Dormant codebase — 159 of 159 significant files have no living knowledge — the codebase as a whole is dormant, not 159 separate risks. Counted over 159 of the 540 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

M3 · Folder & project structure · No src/ separation · ×1

No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

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 — 0/12 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.

X7 · Silent fallback defaults · Silent fallback default in catch · ×1

Silent fallback default in catch core/jazz_ui/src/app/core/pipes/order-by.pipe.ts:31 — `transform` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e84932abb3224d9dbe9c5d9a0c56627c/history.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e84932abb3224d9dbe9c5d9a0c56627c/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	32	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	54	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	0	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	2	artifacts/raw/semgrep-gdpr.json
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	1	artifacts/raw/trivy-fs.json

Run 01a1634a-9db5-7611-9795-49fe0abb44a4 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture: which parts of the code depend on which

At a glance — Code Health · 50% · Weak · gated by R1, X5 ·

At a glance — Architecture · 65% · Adequate · gated by AX10 ·

At a glance — Maturity · 63% · Adequate · gated by D34 ·

At a glance — Readiness · 45% · Weak · gated by D9, D13, R8 ·

At a glance — Security · 59% · Adequate · gated by D28, D29, D30, D43 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts