Repository Analysis

cadence-workflow/cadence

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

3.0 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of cadence-workflow/cadence, a Go project with 9,370 GitHub stars. SynthScan v2.0 examined 907,851 lines of code across 2561 source files, recording 2461 pattern matches distributed across 11 syntactic categories. The overall adjusted score of 3.0 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

3.0
Adjusted Score
3.0
Raw Score
100%
Time Factor
2026-07-13
Last Push
9.4K
Stars
Go
Language
907.9K
Lines of Code
2.6K
Files
2.5K
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 1HIGH 0MEDIUM 134LOW 2326

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 2461 distinct pattern matches across 11 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block2269 hits · 2155 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/server.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
LOWcmd/server/cadence/fx.go1// The MIT License (MIT)COMMENT
LOWcmd/server/cadence/server_test.go1// Copyright (c) 2021 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
2209 more matches not shown…
Decorative Section Separators90 hits · 268 pts
SeverityFileLineSnippetContext
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go537// ┌───────────────────┐ ┌───────────────────┐ ┌────────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go543// └───────────────────┘ └───────────────────┘ └────────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go545// ┌───────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go549// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go551// ┼───────────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go552// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go556// └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go557// ┌────────────────────────┤ │COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go559// ┌─────────▼─────────┐ ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go563// └─────────┬─────────┘ └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go566// ┌─────────▼─────────┐ ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go570// └───────────────────┘ └───────────────────┘ └───────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go578// ┌───────────────────┐ ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐ ┌────────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go584// └───────────────────┘ └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ └────────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go587// ┌───────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go591// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go593// ┼───────────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go594// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go598// └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go599// ┌────────────────────────┤ │COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go601// ┌─────────▼─────────┐ ┌─ ─ ─ ─ ─▼ ─ ─ ─ ─ ┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go605// └─────────┬─────────┘ └─ ─ ─ ─ ─┐ ─ ─ ─ ─ ┘ └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go608// ┌─────────▼─────────┐ ┌─ ─ ─ ─ ─▼ ─ ─ ─ ─ ┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go612// └───────────────────┘ └─ ─ ─ ─ ── ─ ─ ─ ─ ┘ └───────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go694// ┌───────────────────┐ ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐ ┌────────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go700// └───────────────────┘ └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ └────────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go704// ┌───────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go708// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go710// ┼─────────────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go711// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go715// └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go716// ┌────────────────────────┘ │COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go718// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go722// └─────────┬─────────┘ └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go725// ┌─────────▼─────────┐ ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go729// └───────────────────┘ └───────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go736// ┌───────────────────┐ ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐ ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go742// └───────────────────┘ └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go745// ┌───────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go749// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go752// ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go756// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go757// ┌────────────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go759// ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go763// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go766// ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go770// └───────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go858// ┌─ ─ ─ ─ ─ ─ ─ ─ ─ ─┐ ┌───────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go864// └─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ └───────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go869// ┌───────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go873// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go875// ┌─────────┼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go879// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go880// ┼────────────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go883// ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go887// └─────────┬─────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go890// ┌─────────▼─────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go894// └───────────────────┘COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go1011// ┌───────────────────┐ ┌───────────────────┐ ┌────────────────────┐COMMENT
MEDIUMcommon/persistence/nosql/nosql_history_store_test.go1017// └───────────────────┘ └───────────────────┘ └────────────────────┘COMMENT
30 more matches not shown…
Self-Referential Comments36 hits · 106 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…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
Structural Annotation Overuse23 hits · 48 pts
SeverityFileLineSnippetContext
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/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
LOWcommon/persistence/history_manager_test.go1567 // Step 1: Serialize the tokenCOMMENT
LOWcommon/persistence/history_manager_test.go1571 // Step 2: Deserialize the token backCOMMENT
LOWcommon/persistence/history_manager_test.go1575 // Step 3: Compare the original token with the deserialized tokenCOMMENT
LOWcommon/persistence/elasticsearch/es_visibility_store.go644 // Step 1: Convert with elasticsql for the non-LIKE portionCOMMENT
LOWcommon/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
LOWcommon/task/iwrr_node.go268 // Step 2: Cleanup children WITHOUT holding parent lockCOMMENT
LOWcommon/task/iwrr_node.go277 // Step 3: Fast path if no children need removalCOMMENT
LOWcommon/task/iwrr_node.go282 // Step 4: Acquire write lock only when we need to modifyCOMMENT
LOWservice/worker/domaindeprecation/workflow.go80 // Step 1: Activity disables archivalCOMMENT
LOWservice/worker/domaindeprecation/workflow.go90 // Step 2: Deprecate a domainCOMMENT
LOWservice/worker/domaindeprecation/workflow.go100 // Step 3: Start child batch workflow to terminate open workflows of a domainCOMMENT
AI Slop Vocabulary8 hits · 32 pts
SeverityFileLineSnippetContext
MEDIUMdocker/docker-compose-unleash.yml3# and common/dynamicconfig/openfeatureprovider/unleash).COMMENT
MEDIUMdocker/docker-compose-unleash.yml11# docker compose -f docker-compose-unleash.yml up --buildCOMMENT
MEDIUMdocker/docker-compose-unleash.yml21# OpenFeature/Unleash client from ./unleash/bootstrap.json on startup (seeCOMMENT
MEDIUMdocker/docker-compose-unleash.yml22# UNLEASH_BOOTSTRAP_FILE and common/dynamicconfig/openfeatureprovider/unleash'sCOMMENT
MEDIUMdocker/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.go426 // To have a seamless failover experience, cluster should use this forwarding option to forward those APIs to the activCOMMENT
MEDIUMcommon/config/config.go449 // Usage recommendation: when enabling XDC(global domain) feature, either "all-domain-apis-forwarding" or "selected-apCOMMENT
Verbosity Indicators13 hits · 28 pts
SeverityFileLineSnippetContext
LOWcommon/archiver/historyIterator.go219 // We need to check if there's more history batches.COMMENT
LOWcommon/persistence/history_manager_test.go1567 // Step 1: Serialize the tokenCOMMENT
LOWcommon/persistence/history_manager_test.go1571 // Step 2: Deserialize the token backCOMMENT
LOWcommon/persistence/history_manager_test.go1575 // Step 3: Compare the original token with the deserialized tokenCOMMENT
LOWcommon/persistence/elasticsearch/es_visibility_store.go644 // Step 1: Convert with elasticsql for the non-LIKE portionCOMMENT
LOWcommon/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
LOWcommon/task/iwrr_node.go268 // Step 2: Cleanup children WITHOUT holding parent lockCOMMENT
LOWcommon/task/iwrr_node.go277 // Step 3: Fast path if no children need removalCOMMENT
LOWcommon/task/iwrr_node.go282 // Step 4: Acquire write lock only when we need to modifyCOMMENT
LOWservice/worker/domaindeprecation/workflow.go80 // Step 1: Activity disables archivalCOMMENT
LOWservice/worker/domaindeprecation/workflow.go90 // Step 2: Deprecate a domainCOMMENT
LOWservice/worker/domaindeprecation/workflow.go100 // Step 3: 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
LOWscripts/test_multicluster_domain_workflow.sh315 # Check if domain is global domainCOMMENT
LOWscripts/test_multicluster_domain_workflow.sh323 # Check if auto-forwarding would be enabled (global domains typically have this enabled)COMMENT
LOWscripts/test_multicluster_domain_workflow.sh327 # Check if we're dealing with multi-cluster domainCOMMENT
LOWscripts/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.go265 Identity: "user@example.com",CODE
LOWcommon/authorization/oauthAuthorizer_test.go92 Actor: "John Doe",CODE