AI Slop Code Risk Monitor

temporalio/temporal

SlopCodeMonitor badge for temporalio/temporal Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Temporal service

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for temporalio/temporal, a Go project with 24,100 GitHub stars. SynthScan examined 1,152,445 lines of code across 3561 source files, recording 525 pattern matches distributed across 12 syntactic categories. The legacy adjusted pattern signal is 0.5 (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.

0.5
Adjusted Signal
0.5
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
24.1K
Stars
Go
Language
1.2M
Lines of Code
3.6K
Files
525
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 2.3/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 0.1/100 · LOW

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

PR Review Velocity Impact 2.5/100 · LOW

Which changes need focused human review? 525 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 3HIGH 1MEDIUM 18LOW 503

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 525 distinct pattern matches across 12 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 Block485 hits · 482 pts
SeverityFileLineSnippetContext
LOWtemporal/fx.go981// - []go.opentelemetry.io/otel/sdk/trace.BatchSpanProcessorOptionCOMMENT
LOWcmd/tools/test/find_altered_tests.go21// - Target Git Reference (-t): The target Git reference (commit SHA, branch, etc.).COMMENT
LOWcmd/tools/check-dependencies/plan.go41// pseudoRelease is the release implied by a pseudo-version.COMMENT
LOWcmd/tools/check-dependencies/main.go1// check-dependencies validates that key Go module dependencies (go.temporal.io/apiCOMMENT
LOWcmd/tools/check-dependencies/main.go381// --single-branch: fetch only the ref for --branch, not all remote branches.COMMENT
LOWcmd/tools/check-dependencies/main_test.go141 onBranchHash stringCOMMENT
LOWtemporaltest/server_test.go281 // TODO(jlegrone): investigate why custom search attribute missing here while setting it from workflow succeeds.COMMENT
LOWtemporaltest/internal/lite_server.go41 // This is required if Ephemeral is false.COMMENT
LOWtools/ci-notify/datarace.go21 // write/write, so both kinds must be matched.COMMENT
LOWtools/flakereport/doc.go1// Package flakereport implements Bayesian commit bisection for identifying which commitCOMMENT
LOWtools/flakereport/doc.go21//COMMENT
LOWtools/flakereport/doc.go41//COMMENT
LOWtools/flakereport/doc.go61// # OutputCOMMENT
LOWtools/tdbg/util.go101// - week/wCOMMENT
LOWtools/tdbg/util.go141 res := now.Add(time.Duration(-num) * dur) // using server's local timezoneCOMMENT
LOWtools/tdbg/scheduleaudit/loaders.go181// visibilityPageSize is the per-call page size for visibility queries. 1000 is a safe default; the server may clampCOMMENT
LOWtools/tdbg/scheduleaudit/analyzer.go21)COMMENT
LOWdevelop/buf-breaking.sh1#!/usr/bin/env bashCOMMENT
LOWdevelop/github/monitor_test.sh1#!/bin/bashCOMMENT
LOWdevelop/github/memory_monitor.sh1#!/bin/bashCOMMENT
LOWchasm/path_encoder.go21COMMENT
LOWchasm/tree.go41)COMMENT
LOWchasm/tree.go101 // Do NOT set this field directly, use setValueState() method instead.COMMENT
LOWchasm/tree.go121 // transaction) and also the executionState from backend (for previous transactions).COMMENT
LOWchasm/tree.go901 n.updateLastUpdateVersionedTransition()COMMENT
LOWchasm/tree.go2841 NodesWithUncoveredTasks intCOMMENT
LOWchasm/tree.go3001 return errCOMMENT
LOWchasm/tree.go3021 // and hit other undefined issues when root is deleted.COMMENT
LOWchasm/tree.go3881// executed. Intended for use by standby handlers.COMMENT
LOWchasm/task.go21 ScheduledTime time.TimeCOMMENT
LOWchasm/task.go61 }COMMENT
LOWchasm/describe.go1package chasmCOMMENT
LOWchasm/detached_tree.go21 "go.temporal.io/server/service/history/tasks"COMMENT
LOWchasm/visibility.go241// affecting the stored data, but the *commonpb.Payload values are shared.COMMENT
LOWchasm/ref.go41COMMENT
LOWchasm/search_attribute.go21// var testComponentStartTimeSearchAttribute = NewSearchAttributeTime("StartTime", SearchAttributeFieldDateTime01)COMMENT
LOWchasm/context.go21COMMENT
LOWchasm/context.go41 NamespaceEntry() *namespace.NamespaceCOMMENT
LOWchasm/context.go61 // RequestLinks returns the links attached to the given component for the specific requestID.COMMENT
LOWchasm/context.go81 structuredRef(Component) (ComponentRef, error)COMMENT
LOWchasm/context.go121 // nil/empty links removes the entry.COMMENT
LOWchasm/tree_test.go1701COMMENT
LOWchasm/engine.go81 BusinessIDConflictPolicyUseExistingCOMMENT
LOWchasm/engine.go121// must be recorded. It only matters for UpdateComponent().COMMENT
LOWchasm/engine.go141// Fields:COMMENT
LOWchasm/engine.go161// - ExecutionKey: The unique identifier for the execution. This key can be used toCOMMENT
LOWchasm/engine.go241// supplied component ref is validated. Currently only UpdateComponent() honors it; it defaults toCOMMENT
LOWchasm/engine.go261// Type Parameters:COMMENT
LOWchasm/engine.go361// the ref in the transition function. There are some caveats there, check theCOMMENT
LOWchasm/timeskipping.go21// adjust the config via SetTimeSkippingConfig.COMMENT
LOWchasm/lib/namespacereplication/tasks.go641 // — the frontend's retry interceptor and SDK/activity retry re-issue theCOMMENT
LOWchasm/lib/namespacereplication/peer_applier.go41 // PeerApplyResultApplied means the peer accepted the mutation as new stateCOMMENT
LOWchasm/lib/namespacereplication/peer_applier.go61// PeerApplier applies a committed namespace mutation to a single peer cell andCOMMENT
LOWchasm/lib/namespacereplication/component.go121COMMENT
LOW…eplication/gen/namespacereplicationpb/v1/service.pb.go21 // Verify that this generated code is sufficiently up-to-date.COMMENT
LOW…eplication/gen/namespacereplicationpb/v1/message.pb.go281type NamespaceMutation struct {COMMENT
LOWchasm/lib/activity/operator_commands.go141 HeartbeatTimeout: a.GetHeartbeatTimeout(),COMMENT
LOWchasm/lib/activity/operator_commands.go401}COMMENT
LOWchasm/lib/activity/responses.go321COMMENT
LOWchasm/lib/activity/validator.go81// ValidateAndNormalizeActivityAttributes validates and normalizes the common activity request attributes.COMMENT
425 more matches not shown…
Decorative Section Separators10 hits · 30 pts
SeverityFileLineSnippetContext
MEDIUMtests/history_node_cleanup_test.go105 // ── Step 1: start and complete run A ─────────────────────────────────────COMMENT
MEDIUMtests/history_node_cleanup_test.go146 // ── Step 2: reset A → run B ───────────────────────────────────────────────COMMENT
MEDIUMtests/history_node_cleanup_test.go162 // ── Step 3: force-delete run A ────────────────────────────────────────────COMMENT
MEDIUMtests/history_node_cleanup_test.go174 // ── Step 4: force-delete run B ────────────────────────────────────────────COMMENT
MEDIUMtests/history_node_cleanup_test.go183 // ── Assertions ────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/timeskipping_test.go1569 // ── Assertion 1/2/3: the three history events are present. ────────────────COMMENT
MEDIUMtests/timeskipping_test.go1712 // ── Assertion 7: activity-2 events are stamped with virtual time. ─────────COMMENT
MEDIUMtests/timeskipping_test.go1750 // ── Assertion 8: activity-2 timeout task is anchored to wall clock. ──────COMMENT
MEDIUMservice/history/workflow/mutable_state_impl_test.go9129 // ── closeTransactionHandleActivityUserTimerTasks scenarios ──────────────────COMMENT
MEDIUMservice/history/workflow/mutable_state_impl_test.go9248 // closeTransactionRegenerateTimerTasksForTimeSkipping ───────────COMMENT
Hallucination Indicators3 hits · 30 pts
SeverityFileLineSnippetContext
CRITICALservice/matching/physical_task_queue_manager_test.go193 s.tqMgr.backlogMgr.taskReader.gorogrp.Cancel()CODE
CRITICALservice/matching/physical_task_queue_manager_test.go194 s.tqMgr.backlogMgr.taskReader.gorogrp.Wait()CODE
CRITICALservice/history/api/multioperation/api.go195 updateID := uws.updateReq.Request.Request.Meta.GetUpdateId()CODE
AI Slop Vocabulary7 hits · 21 pts
SeverityFileLineSnippetContext
MEDIUMtemporal/fx.go392// into fx providers here. Essentially, we want an `fx.In` object in the server graph, and an `fx.Out` object in theCOMMENT
MEDIUMtests/xdc/activity_timer_task_replication_test.go85// checkpoints. That is the property that matters, and it is robust to however many tasksCOMMENT
MEDIUMcommon/persistence/execution_manager.go535 // try to utilize resp as much as possible, for RebuildMutableState APICOMMENT
MEDIUMcommon/persistence/execution_manager.go954 // try to utilize resp as much as possible, for RebuildMutableState APICOMMENT
MEDIUMservice/matching/scale_manager_test.go212// fixed expected count, this is robust to how many matches happened earlier in the test.COMMENT
MEDIUMservice/frontend/fx.go101 // A more robust approach would require using fx groups but we shouldn't overcomplicate until this becomes an issue.COMMENT
MEDIUMservice/history/tasks/task_category_registry.go26// each entry point that uses it. Essentially, get it from the dependency graph instead of calling this method, unlessCOMMENT
Verbosity Indicators5 hits · 8 pts
SeverityFileLineSnippetContext
LOWtests/versioning_3_test.go5942 // Step 3: CaN run starts on v1. Target=v2, declined=v2 → case 4 suppresses signal.COMMENT
LOWtests/versioning_3_test.go5963 // Step 4: Rollback — set v1 as current again. Target becomes v1.COMMENT
LOWtests/versioning_3_test.go5985 // Step 5: Set v2 as current again. Target goes back to v2.COMMENT
LOWcommon/archiver/history_iterator.go181 // We need to check if there's more history batches.COMMENT
LOWservice/history/statemachine_environment.go147 // for close workflow we need to check if it is still the current runCOMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHtests/client_misc_test.go864// Server complete workflow as requested.COMMENT
Structural Annotation Overuse4 hits · 6 pts
SeverityFileLineSnippetContext
LOWtests/versioning_3_test.go5942 // Step 3: CaN run starts on v1. Target=v2, declined=v2 → case 4 suppresses signal.COMMENT
LOWtests/versioning_3_test.go5963 // Step 4: Rollback — set v1 as current again. Target becomes v1.COMMENT
LOWtests/versioning_3_test.go5985 // Step 5: Set v2 as current again. Target goes back to v2.COMMENT
LOW…on/persistence/transitionhistory/transition_history.go79// NOTE: This function should only be used when there is reloading logic on top of it, since the error returned is aCOMMENT
TODO Padding4 hits · 6 pts
SeverityFileLineSnippetContext
LOWtests/xdc/nexus_request_forwarding_test.go89// TODO: Add test cases for dispatch by endpoint ID once endpoints support replication.COMMENT
LOWtests/xdc/nexus_request_forwarding_test.go266// TODO: Add test cases for dispatch by endpoint ID once endpoints support replication.COMMENT
LOWservice/matching/pri_matcher_test.go645// TODO: Add tests for verifying the validator doesn't consume rate limit tokens.COMMENT
LOWservice/history/replication/executable_sync_hsm_task.go187// TODO: implement the following methods to batch syncHSM task if neededCOMMENT
Example Usage Blocks3 hits · 4 pts
SeverityFileLineSnippetContext
LOWdevelop/github/monitor_test.sh7# Usage:COMMENT
LOWdevelop/github/memory_monitor.sh21# Usage:COMMENT
LOWcommon/log/interface.go11 // Usage example:COMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM…rker/workerdeployment/replaytester/generate_history.sh47# Create the default namespaceCOMMENT
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWservice/matching/counter/map.go87 // don't forget to fix the map:COMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcmd/tools/check-dependencies/main_test.go185 run("config", "user.email", "test@test.com")CODE