AI Slop Code Risk Monitor

cadence-workflow/cadence

SlopCodeMonitor badge for cadence-workflow/cadence Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.

2.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for cadence-workflow/cadence, a Go project with 9,531 GitHub stars. SynthScan examined 1,018,294 lines of code across 2685 source files, recording 2541 pattern matches distributed across 11 syntactic categories. The legacy adjusted pattern signal is 2.7 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

2.7
Adjusted Signal
2.7
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
9.5K
Stars
Go
Language
1.0M
Lines of Code
2.7K
Files
2.5K
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 11.5/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 2448 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

Are imports declared and package/API names verified? 3 finding(s).

Agent Over-Engineering Ratio 1.3/100 · LOW

Are wrappers, guards, and repeated structures necessary? 90 finding(s).

PR Review Velocity Impact 12.9/100 · LOW

Which changes need focused human review? 2541 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 1HIGH 0MEDIUM 136LOW 2404

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 2541 distinct pattern matches across 11 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block2327 hits · 2207 pts
SeverityFileLineSnippetContext
LOWrevive.toml81# [rule.get-return] # existing failures are intentional + desirable, but in principle it's a fine ideaCOMMENT
LOWrevive.toml101# [rule.line-length-limit] # too arbitraryCOMMENT
LOWcmd/bench/main.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWcmd/tools/cli/main.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWcmd/tools/cassandra/main.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWcmd/tools/sql/main.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWcmd/canary/main.go1// Copyright (c) 2019 Uber Technologies, Inc.COMMENT
LOWcmd/server/main.go1// Copyright (c) 2019 Uber Technologies, Inc.COMMENT
LOWcmd/server/cadence/cadence_test.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWcmd/server/cadence/fx_test.go1// The MIT License (MIT)COMMENT
LOWcmd/server/cadence/cadence.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWbench/worker.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/cancellation/workflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/timer/timerWorkflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/timer/launchWorkflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/basic/launchWorkflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/basic/stressWorkflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/common/activities.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/common/constants.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/common/helpers.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/concurrentexec/batchWorkflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/concurrentexec/launchWorkflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/signal/workflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/load/cron/workflow.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/lib/config.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/lib/config.go161 // MaxTimerLatencyInSeconds specifies the maximum latency for the first timer in the workflowCOMMENT
LOWbench/lib/metrics.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/lib/types.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/lib/client.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/lib/context.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWbench/lib/config_test.go1// Copyright (c) 2017-2021 Uber Technologies Inc.COMMENT
LOWtools/linter/funcorder/analyzer.go1// The MIT License (MIT)COMMENT
LOWtools/linter/funcorder/cmd/funcorder/main.go1// The MIT License (MIT)COMMENT
LOWtools/mcp/main.go1// The MIT License (MIT)COMMENT
LOWtools/cli/render.go1// Copyright (c) 2022 Uber Technologies, Inc.COMMENT
LOWtools/cli/app_test.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/domain.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/schedule_commands.go1// Copyright (c) 2026 Uber Technologies, Inc.COMMENT
LOWtools/cli/admin_failover_commands_test.go1// Copyright (c) 2017-2020 Uber Technologies Inc.COMMENT
LOWtools/cli/admin_config_store_commands_test.go1// The MIT License (MIT)COMMENT
LOWtools/cli/utils_test.go1// Copyright (c) 2022 Uber Technologies, Inc.COMMENT
LOWtools/cli/task_list_commands.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/histogram_test.go1// The MIT License (MIT)COMMENT
LOWtools/cli/admin_timers.go1// The MIT License (MIT)COMMENT
LOWtools/cli/defs.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/admin_cluster_commands_test.go1// The MIT License (MIT)COMMENT
LOWtools/cli/admin_elastic_search_commands.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/isolation-groups.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/admin_db_clean_command.go1// The MIT License (MIT)COMMENT
LOWtools/cli/schedule_commands_test.go1// Copyright (c) 2026 Uber Technologies, Inc.COMMENT
LOWtools/cli/domain_migration_command.go1// The MIT License (MIT)COMMENT
LOWtools/cli/factory.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/workflow_batch_commands_test.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/domain_utils.go1// Copyright (c) 2019 Uber Technologies, Inc.COMMENT
LOWtools/cli/domain_migration_command_test.go1// The MIT License (MIT)COMMENT
LOWtools/cli/isolation_groups_test.go1// The MIT License (MIT)COMMENT
LOWtools/cli/admin_commands.go1// Copyright (c) 2017-2020 Uber Technologies Inc.COMMENT
LOWtools/cli/admin_db_decode_thrift_test.go1// The MIT License (MIT)COMMENT
LOWtools/cli/workflow_batch_commands.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWtools/cli/admin_commands_test.go1// The MIT License (MIT)COMMENT
2267 more matches not shown…
Decorative Section Separators90 hits · 268 pts
SeverityFileLineSnippetContext
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go537// ┌───────────────────┐ ┌───────────────────┐ ┌────────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go543// └───────────────────┘ └───────────────────┘ └────────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go545// ┌───────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go549// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go551// ┼───────────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go552// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go556// └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go557// ┌────────────────────────┤ │COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go559// ┌─────────▼─────────┐ ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go563// └─────────┬─────────┘ └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go566// ┌─────────▼─────────┐ ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go570// └───────────────────┘ └───────────────────┘ └───────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go578// ┌───────────────────┐ ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐ ┌────────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go584// └───────────────────┘ └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ └────────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go587// ┌───────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go591// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go593// ┼───────────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go594// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go598// └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go599// ┌────────────────────────┤ │COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go601// ┌─────────▼─────────┐ ┌─ ─ ─ ─ ─▼ ─ ─ ─ ─ ┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go605// └─────────┬─────────┘ └─ ─ ─ ─ ─┐ ─ ─ ─ ─ ┘ └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go608// ┌─────────▼─────────┐ ┌─ ─ ─ ─ ─▼ ─ ─ ─ ─ ┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go612// └───────────────────┘ └─ ─ ─ ─ ── ─ ─ ─ ─ ┘ └───────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go694// ┌───────────────────┐ ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐ ┌────────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go700// └───────────────────┘ └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ └────────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go704// ┌───────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go708// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go710// ┼─────────────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go711// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go715// └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go716// ┌────────────────────────┘ │COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go718// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go722// └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go725// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go729// └───────────────────┘ └───────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go736// ┌───────────────────┐ ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐ ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go742// └───────────────────┘ └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go745// ┌───────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go749// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go752// ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go756// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go757// ┌────────────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go759// ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go763// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go766// ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go770// └───────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go858// ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐ ┌───────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go864// └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ └───────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go869// ┌───────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go873// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go875// ┌─────────┼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go879// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go880// ┼────────────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go883// ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go887// └─────────┬─────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go890// ┌─────────▼─────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go894// └───────────────────┘COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go1011// ┌───────────────────┐ ┌───────────────────┐ ┌────────────────────┐COMMENT
MEDIUM⚡common/persistence/nosql/nosql_history_store_test.go1017// └───────────────────┘ └───────────────────┘ └────────────────────┘COMMENT
30 more matches not shown…
Self-Referential Comments38 hits · 112 pts
SeverityFileLineSnippetContext
MEDIUMdocker/dev/cassandra-opensearch-kafka.yml30 OPENSEARCH_HOSTS: '["http://opensearch:9200"]' # Define the OpenSearch nodes that OpenSearch Dashboards will queryCODE
MEDIUMdocker/dev/cassandra-opensearch-kafka-migration.yml36 OPENSEARCH_HOSTS: '["https://opensearch:9200"]' # Define the OpenSearch nodes that OpenSearch Dashboards will querCODE
MEDIUM…_simulation_activeactive_same_wfid_signalwithstart.yml1# This file is used as dynamicconfig override for "activeactive_same_wfid_signalwithstart" replication simulation scenarCOMMENT
MEDIUM…lication_simulation_activeactive_regional_failover.yml1# This file is used as dynamicconfig override for "activeactive_regional_failover" replication simulation scenario confiCOMMENT
MEDIUM…onfig/replication_simulation_activityretryfailover.yml1# This file is used as dynamicconfig override for "activityretryfailover" replication simulation scenario configured viaCOMMENT
MEDIUM…on_activeactive_signalwithstart_terminateifrunning.yml1# This file is used as dynamicconfig override for "activeactive" replication simulation scenario configured via simulatiCOMMENT
MEDIUM…n_simulation_activeactive_start_terminateifrunning.yml1# This file is used as dynamicconfig override for "activeactive" replication simulation scenario configured via simulatiCOMMENT
MEDIUMconfig/dynamicconfig/replication_simulation_reset.yml1# This file is used as dynamicconfig override for "reset" replication simulation scenario configured via simulation/replCOMMENT
MEDIUM…icconfig/replication_simulation_activeactive_child.yml1# This file is used as dynamicconfig override for "activeactive" replication simulation scenario configured via simulatiCOMMENT
MEDIUM…plication_simulation_activepassive_to_activeactive.yml1# This file is used as dynamicconfig override for "activepassive_to_activeactive" replication simulation scenario configCOMMENT
MEDIUM…micconfig/replication_simulation_activeactive_cron.yml1# This file is used as dynamicconfig override for "activeactive_cron" replication simulation scenario configured via simCOMMENT
MEDIUM…_simulation_activeactive_invalid_cluster_attribute.yml1# This file is used as dynamicconfig override for "activeactive" replication simulation scenario configured via simulatiCOMMENT
MEDIUM…n_activeactive_regional_failover_start_same_wfid_2.yml1# This file is used as dynamicconfig override for "activeactive_regional_failover_start_same_wfid_2" replication simulatCOMMENT
MEDIUM…/dynamicconfig/replication_simulation_activeactive.yml1# This file is used as dynamicconfig override for "activeactive" replication simulation scenario configured via simulatiCOMMENT
MEDIUM…icconfig/replication_simulation_clusterredirection.yml1# This file is used as dynamicconfig override for "clusterredirection" replication simulation scenario configured via siCOMMENT
MEDIUM…nfig/replication_simulation_activeactive_same_wfid.yml1# This file is used as dynamicconfig override for "activeactive" replication simulation scenario configured via simulatiCOMMENT
MEDIUM…ynamicconfig/replication_simulation_budget_manager.yml1# This file is used as dynamicconfig override for "budget_manager" replication simulation scenarioCOMMENT
MEDIUM…ion_activeactive_regional_failover_start_same_wfid.yml1# This file is used as dynamicconfig override for "activeactive_regional_failover_start_same_wfid" replication simulatioCOMMENT
MEDIUM…ion_activeactive_same_wfid_signalwithstart_delayed.yml1# This file is used as dynamicconfig override for "activeactive_same_wfid_signalwithstart_delayed" replication simulatioCOMMENT
MEDIUMconfig/dynamicconfig/replication_simulation_default.yml1# This file is used as dynamicconfig override for "default" replication simulation scenario configured via simulation/reCOMMENT
MEDIUM…estdata/replication_simulation_clusterredirection.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…estdata/replication_simulation_activeactive_child.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…tion/testdata/replication_simulation_activeactive.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…lication_simulation_activepassive_to_activeactive.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…on_activeactive_regional_failover_start_same_wfid.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…_simulation_activeactive_start_terminateifrunning.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…simulation_activeactive_invalid_cluster_attribute.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…on/testdata/replication_simulation_budget_manager.yaml1# This file is a replication simulation scenario spec for testing the budget manager.COMMENT
MEDIUM…_activeactive_regional_failover_start_same_wfid_2.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…testdata/replication_simulation_activeactive_cron.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…plication/testdata/replication_simulation_default.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…ication_simulation_activeactive_regional_failover.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…replication/testdata/replication_simulation_reset.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…n_activeactive_signalwithstart_terminateifrunning.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…ata/replication_simulation_activeactive_same_wfid.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…simulation_activeactive_same_wfid_signalwithstart.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…on_activeactive_same_wfid_signalwithstart_delayed.yaml1# This file is a replication simulation scenario spec.COMMENT
MEDIUM…data/replication_simulation_activityretryfailover.yaml1# This file is a replication simulation scenario spec.COMMENT
Structural Annotation Overuse42 hits · 76 pts
SeverityFileLineSnippetContext
LOW.gitar/rules/blank-imports-library.md29### Step 1: Identify Go files with blank importsCOMMENT
LOW.gitar/rules/blank-imports-library.md47### Step 2: Categorize by locationCOMMENT
LOW.gitar/rules/blank-imports-library.md62### Step 3: Identify common violating patternsCOMMENT
LOW.gitar/rules/blank-imports-library.md81### Step 4: Check if moved to main.goCOMMENT
LOW.gitar/rules/architecture-separation.md25### Step 1: Check for new initialization logic in cmd/serverCOMMENT
LOW.gitar/rules/architecture-separation.md56### Step 2: Identify changes to service/* packagesCOMMENT
LOW.gitar/rules/architecture-separation.md63### Step 3: Check for hard-coded infrastructure types in service/*COMMENT
LOW.gitar/rules/architecture-separation.md85### Step 4: Check for environment-based conditionals in service/*COMMENT
LOW⚡.gitar/rules/assign-maintainer-reviewer.md18### Step 1: Identify the PR authorCOMMENT
LOW⚡.gitar/rules/assign-maintainer-reviewer.md22### Step 2: Build the maintainer list from MAINTAINERS.mdCOMMENT
LOW⚡.gitar/rules/assign-maintainer-reviewer.md26### Step 3: Check if the author is a maintainerCOMMENT
LOW⚡.gitar/rules/assign-maintainer-reviewer.md32### Step 4: Assign a maintainer (for non-maintainer PRs only)COMMENT
LOW.gitar/rules/assign-maintainer-reviewer.md48### Step 5: Post a welcome comment (for non-maintainer PRs only)COMMENT
LOW.gitar/rules/no-license-headers.md22### Step 1: Identify Go files with license headersCOMMENT
LOW.gitar/rules/no-license-headers.md33### Step 2: Distinguish headers from legitimate referencesCOMMENT
LOW.gitar/rules/daemon-v2-migration.md39### Step 1: Check if PR modifies files that use common.DaemonCOMMENT
LOW.gitar/rules/daemon-v2-migration.md49### Step 2: Determine migration scopeCOMMENT
LOW.gitar/rules/daemon-v2-migration.md61### Step 3: Provide migration guidanceCOMMENT
LOW⚡.gitar/rules/restrict-workflow-changes.md23### Step 1: Get the list of changed filesCOMMENT
LOW⚡.gitar/rules/restrict-workflow-changes.md30### Step 2: Check author against CODEOWNERSCOMMENT
LOW⚡.gitar/rules/restrict-workflow-changes.md36### Step 3: Report when a non-maintainer touches workflow filesCOMMENT
LOW.gitar/rules/issue-linking-required.md95### Step 1: Check Skip ConditionsCOMMENT
LOW.gitar/rules/issue-linking-required.md107### Step 2: Search for Issue LinksCOMMENT
LOW.gitar/rules/issue-linking-required.md119### Step 3: Report StatusCOMMENT
LOWdocs/howtos/update-dynamic-config.md57### Step 1: List Current Config ValuesCOMMENT
LOWdocs/howtos/update-dynamic-config.md92### Step 2: Get Effective Value for a DomainCOMMENT
LOWdocs/howtos/update-dynamic-config.md111### Step 3: Update Config ValuesCOMMENT
LOWdocs/howtos/update-dynamic-config.md206### Step 4: Verify the UpdateCOMMENT
LOWdocs/howtos/update-dynamic-config.md225### Step 5: Restore to Defaults (if needed)COMMENT
LOW⚡common/persistence/history_manager_test.go1567 // Step 1: Serialize the tokenCOMMENT
LOW⚡common/persistence/history_manager_test.go1571 // Step 2: Deserialize the token backCOMMENT
LOW⚡common/persistence/history_manager_test.go1575 // Step 3: Compare the original token with the deserialized tokenCOMMENT
LOW⚡common/persistence/elasticsearch/es_visibility_store.go644 // Step 1: Convert with elasticsql for the non-LIKE portionCOMMENT
LOW⚡common/persistence/elasticsearch/es_visibility_store.go653 // Step 2: Replace dummy nodes with wildcard queries in-placeCOMMENT
LOWcommon/task/iwrr_node.go254 // Step 1: Take snapshot of children with read lockCOMMENT
LOW⚡common/task/iwrr_node.go268 // Step 2: Cleanup children WITHOUT holding parent lockCOMMENT
LOW⚡common/task/iwrr_node.go277 // Step 3: Fast path if no children need removalCOMMENT
LOW⚡common/task/iwrr_node.go282 // Step 4: Acquire write lock only when we need to modifyCOMMENT
LOWservice/worker/domaindeprecation/workflow.go82 // Step 1: Check for active pollers (skipped when Force is set)COMMENT
LOW⚡service/worker/domaindeprecation/workflow.go94 // Step 2: Activity disables archivalCOMMENT
LOW⚡service/worker/domaindeprecation/workflow.go104 // Step 3: Deprecate a domainCOMMENT
LOW⚡service/worker/domaindeprecation/workflow.go114 // Step 4: Start child batch workflow to terminate open workflows of a domainCOMMENT
AI Slop Vocabulary8 hits · 32 pts
SeverityFileLineSnippetContext
MEDIUM⚡docker/docker-compose-unleash.yml3# and common/dynamicconfig/openfeatureprovider/unleash).COMMENT
MEDIUM⚡docker/docker-compose-unleash.yml11# docker compose -f docker-compose-unleash.yml up --buildCOMMENT
MEDIUM⚡docker/docker-compose-unleash.yml21# OpenFeature/Unleash client from ./unleash/bootstrap.json on startup (seeCOMMENT
MEDIUM⚡docker/docker-compose-unleash.yml22# UNLEASH_BOOTSTRAP_FILE and common/dynamicconfig/openfeatureprovider/unleash'sCOMMENT
MEDIUM⚡docker/docker-compose-unleash.yml24# even before the unleash service itself finishes starting.COMMENT
MEDIUMdocker/docker-compose-unleash.yml74 # Backend/server-side token the Go client (via our openfeatureprovider/unleashCOMMENT
MEDIUMcommon/config/config.go403 // To have a seamless failover experience, cluster should use this forwarding option to forward those APIs to the activCOMMENT
MEDIUMcommon/config/config.go438 // Usage recommendation: when enabling XDC(global domain) feature, either "all-domain-apis-forwarding" or "selected-apCOMMENT
Verbosity Indicators14 hits · 29 pts
SeverityFileLineSnippetContext
LOWcommon/archiver/historyIterator.go219 // We need to check if there's more history batches.COMMENT
LOW⚡common/persistence/history_manager_test.go1567 // Step 1: Serialize the tokenCOMMENT
LOW⚡common/persistence/history_manager_test.go1571 // Step 2: Deserialize the token backCOMMENT
LOW⚡common/persistence/history_manager_test.go1575 // Step 3: Compare the original token with the deserialized tokenCOMMENT
LOW⚡common/persistence/elasticsearch/es_visibility_store.go644 // Step 1: Convert with elasticsql for the non-LIKE portionCOMMENT
LOW⚡common/persistence/elasticsearch/es_visibility_store.go653 // Step 2: Replace dummy nodes with wildcard queries in-placeCOMMENT
LOWcommon/task/iwrr_node.go254 // Step 1: Take snapshot of children with read lockCOMMENT
LOW⚡common/task/iwrr_node.go268 // Step 2: Cleanup children WITHOUT holding parent lockCOMMENT
LOW⚡common/task/iwrr_node.go277 // Step 3: Fast path if no children need removalCOMMENT
LOW⚡common/task/iwrr_node.go282 // Step 4: Acquire write lock only when we need to modifyCOMMENT
LOWservice/worker/domaindeprecation/workflow.go82 // Step 1: Check for active pollers (skipped when Force is set)COMMENT
LOW⚡service/worker/domaindeprecation/workflow.go94 // Step 2: Activity disables archivalCOMMENT
LOW⚡service/worker/domaindeprecation/workflow.go104 // Step 3: Deprecate a domainCOMMENT
LOW⚡service/worker/domaindeprecation/workflow.go114 // Step 4: Start child batch workflow to terminate open workflows of a domainCOMMENT
Redundant / Tautological Comments9 hits · 16 pts
SeverityFileLineSnippetContext
LOWdocker/docker-compose-custom-config.yml54 # Set this to use a custom config file instead of config_template.yamlCOMMENT
LOWscripts/test_multicluster_domain_workflow.sh109 # Check if domain is globalCOMMENT
LOWscripts/test_multicluster_domain_workflow.sh214 # Check if metric value is greater than 0COMMENT
LOWscripts/test_multicluster_domain_workflow.sh230 # Check if we can find evidence of metric increments in logs or responsesCOMMENT
LOWscripts/test_multicluster_domain_workflow.sh298 # Check if domain is global (required for forwarding)COMMENT
LOW⚡scripts/test_multicluster_domain_workflow.sh315 # Check if domain is global domainCOMMENT
LOW⚡scripts/test_multicluster_domain_workflow.sh323 # Check if auto-forwarding would be enabled (global domains typically have this enabled)COMMENT
LOW⚡scripts/test_multicluster_domain_workflow.sh327 # Check if we're dealing with multi-cluster domainCOMMENT
LOW⚡scripts/test_multicluster_domain_workflow.sh333 # Check if DescribeWorkflowExecution was called (which would trigger the function)COMMENT
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICALservice/history/queuev2/queue_scheduled.go224 q.timerGate.Update(q.base.newVirtualSliceState.Range.InclusiveMinTaskKey.GetScheduledTime())CODE
Example Usage Blocks6 hits · 9 pts
SeverityFileLineSnippetContext
LOWdocker/docker-compose-custom-config.yml4# Usage:COMMENT
LOWdocker/docker-compose-local.override.yaml4# Usage:COMMENT
LOWsimulation/matching/run.sh5# Usage:COMMENT
LOWsimulation/history/run.sh5# Usage:COMMENT
LOWsimulation/replication/run.sh5# Usage:COMMENT
LOWcommon/types/mapper/testutils/fuzz_mapper.go127// Example usage:COMMENT
TODO Padding4 hits · 6 pts
SeverityFileLineSnippetContext
LOWcommon/mapq/dispatcher/dispatcher.go71 // TODO: implementCOMMENT
LOWcommon/persistence/sql/sql_execution_store_util.go714 // TODO: implement creating tasks for other categoriesCOMMENT
LOWcommon/persistence/sql/sql_execution_store_util.go730 // TODO: implement creating tasks for other categoriesCOMMENT
LOWservice/history/queue/transfer_queue_validator.go139 // TODO: implement an event logger for queue processor and dump all events when this validation fails.COMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWcommon/types/testdata/schedule.go271 Identity: "user@example.com",CODE
LOWcommon/authorization/oauthAuthorizer_test.go92 Actor: "John Doe",CODE