AI Slop Code Risk Monitor

cortexproject/cortex

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

A horizontally scalable, highly available, multi-tenant, long term Prometheus.

1.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for cortexproject/cortex, a Go project with 5,877 GitHub stars. SynthScan examined 383,726 lines of code across 1242 source files, recording 710 pattern matches distributed across 11 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.7
Adjusted Signal
1.7
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
5.9K
Stars
Go
Language
383.7K
Lines of Code
1.2K
Files
710
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 6.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.5/100 · LOW

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

Agent Over-Engineering Ratio 1.2/100 · LOW

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

PR Review Velocity Impact 10.0/100 · LOW

Which changes need focused human review? 710 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 3MEDIUM 30LOW 674

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 710 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 Block630 hits · 425 pts
SeverityFileLineSnippetContext
LOWintegration/util.go61 if err != nil {COMMENT
LOW…tegration/integration_memberlist_single_binary_test.go361COMMENT
LOW…tegration/integration_memberlist_single_binary_test.go381// SuspicionMaxTimeoutMult (6x) that value and only shrinking as other nodes confirm theCOMMENT
LOWintegration/query_fuzz_test.go2281// by the PromQL "found duplicate series for the match group" many-to-many error.COMMENT
LOWintegration/query_fuzz_test.go2561 if strings.Contains(queryStr, "predict_linear") {COMMENT
LOWintegration/e2e/service.go241// NetworkEndpoint returns internal service endpoint (host:port) for given internal port.COMMENT
LOWwebsite/config.toml101# Enable Lunr.js offline searchCOMMENT
LOW…cs/configuration/single-process-config-blocks-tls.yaml61 sync_dir: /tmp/cortex/tsdb-syncCOMMENT
LOWdocs/configuration/single-process-config-blocks.yaml61 # secret_access_key: "TODO"COMMENT
LOWdocs/configuration/config-file-reference.md61[target: <string> | default = "all"]COMMENT
LOWdocs/configuration/config-file-reference.md101COMMENT
LOWdocs/configuration/config-file-reference.md181 # CLI flag: -parquet-converter.conversion-intervalCOMMENT
LOWdocs/configuration/config-file-reference.md281 # Time since last heartbeat before parquet-converter will be removed fromCOMMENT
LOWdocs/configuration/config-file-reference.md301COMMENT
LOWdocs/configuration/config-file-reference.md321 # The scanning strategy depends on theCOMMENT
LOWdocs/configuration/config-file-reference.md361 # If a querier disconnects without sending notification about gracefulCOMMENT
LOWdocs/configuration/config-file-reference.md401 # Maximum delay when backing off.COMMENT
LOWdocs/configuration/config-file-reference.md421 # certificate to be configured.COMMENT
LOWdocs/configuration/config-file-reference.md461# Alertmanager is served via a reverse proxy). Used for generating relative andCOMMENT
LOWdocs/configuration/config-file-reference.md541COMMENT
LOWdocs/configuration/config-file-reference.md561 # shutdown and restored at startup.COMMENT
LOWdocs/configuration/config-file-reference.md581COMMENT
LOWdocs/configuration/config-file-reference.md621 # Time to wait between peers to send notifications.COMMENT
LOWdocs/configuration/config-file-reference.md641# Maximum number of concurrent GET API requests before returning an error.COMMENT
LOWdocs/configuration/config-file-reference.md661 # with the server. Also requires the key path to be configured.COMMENT
LOWdocs/configuration/config-file-reference.md701# The interval between persisting the current alertmanager state (notificationCOMMENT
LOWdocs/configuration/config-file-reference.md761 # be useful in local dev/test environments while using an S3-compatibleCOMMENT
LOWdocs/configuration/config-file-reference.md801 # CLI flag: -alertmanager-storage.s3.http.insecure-skip-verifyCOMMENT
LOWdocs/configuration/config-file-reference.md841 # CLI flag: -alertmanager-storage.azure.account-nameCOMMENT
LOWdocs/configuration/config-file-reference.md861 [endpoint_suffix: <string> | default = "blob.core.windows.net"]COMMENT
LOWdocs/configuration/config-file-reference.md881 [idle_conn_timeout: <duration> | default = 1m30s]COMMENT
LOWdocs/configuration/config-file-reference.md961 # OpenStack Swift user's domain name.COMMENT
LOWdocs/configuration/config-file-reference.md1001 # data is received on a request.COMMENT
LOWdocs/configuration/config-file-reference.md1041 # CLI flag: -alertmanager-storage.oci.private-key-passphraseCOMMENT
LOWdocs/configuration/config-file-reference.md1101# CLI flag: -blocks-storage.backendCOMMENT
LOWdocs/configuration/config-file-reference.md1121 # CLI flag: -blocks-storage.s3.disable-dualstackCOMMENT
LOWdocs/configuration/config-file-reference.md1141 [signature_version: <string> | default = "v4"]COMMENT
LOWdocs/configuration/config-file-reference.md1181 # the request headers if the request has an Expect header. 0 to send theCOMMENT
LOWdocs/configuration/config-file-reference.md1201 # GCS bucket nameCOMMENT
LOWdocs/configuration/config-file-reference.md1221 # ignored if `connection-string` is set. Use this method over `account-key` ifCOMMENT
LOWdocs/configuration/config-file-reference.md1241 # CLI flag: -blocks-storage.azure.msi-resourceCOMMENT
LOWdocs/configuration/config-file-reference.md1261 # CLI flag: -blocks-storage.azure.http.insecure-skip-verifyCOMMENT
LOWdocs/configuration/config-file-reference.md1341 # OpenStack Swift project name (v2,v3 auth only).COMMENT
LOWdocs/configuration/config-file-reference.md1361 [container_name: <string> | default = ""]COMMENT
LOWdocs/configuration/config-file-reference.md1421 # The maximum number of request attempts when encountering recoverable errors.COMMENT
LOWdocs/configuration/config-file-reference.md1441COMMENT
LOWdocs/configuration/config-file-reference.md1461 # When the limit is reached, new requests are rejected with HTTP 503. 0 toCOMMENT
LOWdocs/configuration/config-file-reference.md1481 # (roughly) strongly consistent.COMMENT
LOWdocs/configuration/config-file-reference.md1501 [enabled_items: <list of string> | default = []]COMMENT
LOWdocs/configuration/config-file-reference.md1521 # CLI flag: -blocks-storage.bucket-store.index-cache.memcached.max-async-concurrencyCOMMENT
LOWdocs/configuration/config-file-reference.md1541 # stored. If set to 0, no maximum size is enforced.COMMENT
LOWdocs/configuration/config-file-reference.md1561 # becomes half-open. If set to 0, by default open duration is 60COMMENT
LOWdocs/configuration/config-file-reference.md1581 [enabled_items: <list of string> | default = []]COMMENT
LOWdocs/configuration/config-file-reference.md1641 # Client write timeout.COMMENT
LOWdocs/configuration/config-file-reference.md1661 # If not set, the host's root CA certificates are used.COMMENT
LOWdocs/configuration/config-file-reference.md1681 # CLI flag: -blocks-storage.bucket-store.index-cache.redis.set-async.circuit-breaker.enabledCOMMENT
LOWdocs/configuration/config-file-reference.md1701 [consecutive_failures: <int> | default = 5]COMMENT
LOWdocs/configuration/config-file-reference.md1741 memcached:COMMENT
LOWdocs/configuration/config-file-reference.md1761COMMENT
LOWdocs/configuration/config-file-reference.md1781 [max_item_size: <int> | default = 1048576]COMMENT
570 more matches not shown…
Decorative Section Separators20 hits · 90 pts
SeverityFileLineSnippetContext
MEDIUM⚡pkg/cortex/modules.go379// ┌──────────────────┐ QF to ┌──────────────────┐COMMENT
MEDIUM⚡pkg/cortex/modules.go381// │ router │──────────────▶│ frontend worker │COMMENT
MEDIUM⚡pkg/cortex/modules.go383// └──────────────────┘ └──────────────────┘COMMENT
MEDIUM⚡pkg/cortex/modules.go387// microservice ┌──────────────────┐ │COMMENT
MEDIUM⚡pkg/cortex/modules.go389// ─ ─ ─ ─▶│ router │◀─────┘COMMENT
MEDIUM⚡pkg/cortex/modules.go391// └──────────────────┘COMMENT
MEDIUM⚡pkg/cortex/modules.go394// /metadata & /chunk ┌─────────────────────┼─────────────────────┐COMMENT
MEDIUM⚡pkg/cortex/modules.go398// ┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐COMMENT
MEDIUM⚡pkg/cortex/modules.go402// └──────────────────┘ └──────────────────┘ └──────────────────┘COMMENT
MEDIUM⚡pkg/cortex/modules.go404// │ └──────────┬──────────┘COMMENT
MEDIUM⚡pkg/cortex/modules.go406// │ ┌──────────────────┐COMMENT
MEDIUM⚡pkg/cortex/modules.go408// └──────────────────────│ Prometheus API │COMMENT
MEDIUM⚡pkg/cortex/modules.go410// └──────────────────┘COMMENT
MEDIUM⚡pkg/util/services/service.go44// ┌────────────────────────────────────────────────────────────────────┐COMMENT
MEDIUM⚡pkg/util/services/service.go47// ┌─────┐ ┌──────────┐ ┌─────────┐ ┌──────────┐ ┌────────────┐COMMENT
MEDIUM⚡pkg/util/services/service.go48// │ New │─────▶│ Starting │─────▶│ Running │────▶│ Stopping │───┬─▶│ Terminated │COMMENT
MEDIUM⚡pkg/util/services/service.go49// └─────┘ └──────────┘ └─────────┘ └──────────┘ │ └────────────┘COMMENT
MEDIUM⚡pkg/util/services/service.go52// │ │ ┌────────┐COMMENT
MEDIUM⚡pkg/util/services/service.go53// └──────────────────────────────────────────┴──▶│ Failed │COMMENT
MEDIUM⚡pkg/util/services/service.go54// └────────┘COMMENT
Structural Annotation Overuse29 hits · 50 pts
SeverityFileLineSnippetContext
LOW⚡…site/content/en/blog/2025/readonly-ingester-scaling.md38### Step 1: Transition to READONLYCOMMENT
LOW⚡…site/content/en/blog/2025/readonly-ingester-scaling.md47### Step 2: Monitor Data Status (Optional)COMMENT
LOW⚡…site/content/en/blog/2025/readonly-ingester-scaling.md54### Step 3: Choose Removal StrategyCOMMENT
LOW⚡…site/content/en/blog/2025/readonly-ingester-scaling.md62### Step 4: Remove IngestersCOMMENT
LOWdocs/blocks-storage/migrate-from-chunks-to-blocks.md33## Step 1: PreparationCOMMENT
LOWdocs/blocks-storage/migrate-from-chunks-to-blocks.md77## Step 2: Ingesters migrationCOMMENT
LOWdocs/blocks-storage/migrate-from-chunks-to-blocks.md104## Step 3: CleanupCOMMENT
LOWdocs/getting-started/single-binary.md62## Step 1: Clone the RepositoryCOMMENT
LOWdocs/getting-started/single-binary.md71## Step 2: Start the ServicesCOMMENT
LOWdocs/getting-started/single-binary.md94## Step 3: Verify Services Are RunningCOMMENT
LOWdocs/getting-started/single-binary.md113## Step 4: Verify Data FlowCOMMENT
LOWdocs/getting-started/single-binary.md152## Step 5: Configure Recording and Alerting Rules (Optional)COMMENT
LOWdocs/getting-started/single-binary.md196## Step 6: Configure Alertmanager (Optional)COMMENT
LOWdocs/getting-started/single-binary.md210## Step 7: Per-Tenant Alert Generator URLs (Optional)COMMENT
LOWdocs/getting-started/microservices.md84## Step 1: Create a Kubernetes ClusterCOMMENT
LOWdocs/getting-started/microservices.md105## Step 2: Configure Helm RepositoriesCOMMENT
LOW⚡docs/getting-started/microservices.md116## Step 3: Clone the RepositoryCOMMENT
LOW⚡docs/getting-started/microservices.md125## Step 4: Create the Cortex NamespaceCOMMENT
LOW⚡docs/getting-started/microservices.md133## Step 5: Deploy SeaweedFS (S3-Compatible Storage)COMMENT
LOWdocs/getting-started/microservices.md187## Step 6: Deploy CortexCOMMENT
LOWdocs/getting-started/microservices.md229## Step 7: Deploy PrometheusCOMMENT
LOWdocs/getting-started/microservices.md252## Step 8: Deploy GrafanaCOMMENT
LOWdocs/getting-started/microservices.md292## Step 9: Access the ServicesCOMMENT
LOWdocs/getting-started/microservices.md317## Step 10: Verify Data FlowCOMMENT
LOWdocs/getting-started/microservices.md365## Step 11: Configure Rules and Alerts (Optional)COMMENT
LOWdocs/getting-started/microservices.md412## Step 12: Configure Alertmanager (Optional)COMMENT
LOW⚡pkg/util/grpcclient/signing_handler_test.go168 // Step 2: Distributor redeployed with newKey; ingester still in transition.COMMENT
LOW⚡pkg/util/grpcclient/signing_handler_test.go173 // Step 3: Ingester redeployed with newKey only.COMMENT
LOWpkg/ingester/pushstream_security_test.go119 // Step 2: Attacker requests to write into "tenant-B"COMMENT
Hallucination Indicators3 hits · 30 pts
SeverityFileLineSnippetContext
CRITICALpkg/ingester/ingester.go3031 blockRanges := i.cfg.BlocksStorageConfig.TSDB.BlockRanges.ToMilliseconds()CODE
CRITICALpkg/ingester/ingester.go3075 blockRetentionPeriod: i.cfg.BlocksStorageConfig.TSDB.Retention.Milliseconds(),CODE
CRITICALpkg/ingester/ingester.go3093 RetentionDuration: i.cfg.BlocksStorageConfig.TSDB.Retention.Milliseconds(),CODE
Slop Phrases5 hits · 15 pts
SeverityFileLineSnippetContext
MEDIUM…nfiguration/single-process-config-blocks-gossip-1.yaml73 # Cortex of course supports multiple options (S3, GCS, Azure), but for demonstration purposesCOMMENT
MEDIUM…nfiguration/single-process-config-blocks-gossip-2.yaml72 # Cortex of course supports multiple options (S3, GCS, Azure), but for demonstration purposesCOMMENT
MEDIUM⚡docs/getting-started/grafana-values.yaml456## 3. attach a policy to the role, you can use a built in policy called CloudWatchReadOnlyAccessCOMMENT
LOW⚡docs/getting-started/grafana-values.yaml466## make sure to replace arn:aws:iam::123456789000:role/iam-role-name-here with your role arnCOMMENT
LOW⚡docs/getting-started/grafana-values.yaml466## make sure to replace arn:aws:iam::123456789000:role/iam-role-name-here with your role arnCOMMENT
AI Response Leakage2 hits · 15 pts
SeverityFileLineSnippetContext
HIGHdocs/guides/overrides-exporter.md30# In this example, we're overriding ingestion limits for a single tenant.COMMENT
HIGHdocs/guides/overrides-exporter-runtime.yaml2# In this example, we're overriding ingestion limits for a single tenant.COMMENT
Self-Referential Comments4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUM…blocks-storage-swift-single-binary/config/runtime.yaml1# This file is left empty. It can be configured with overrides or other runtime config.COMMENT
MEDIUMdocs/getting-started/runtime-config.yaml2# This file is hot-reloaded by Cortex without requiring a restart.COMMENT
MEDIUMdocs/getting-started/grafana-values.yaml51## Create a headless service for the deploymentCOMMENT
MEDIUMdocs/getting-started/grafana-values.yaml1326# Create a dynamic manifests via values:COMMENT
Fake / Example Data10 hits · 10 pts
SeverityFileLineSnippetContext
LOW…opment/tsdb-blocks-storage-s3/config/alertmanager.yaml5 smtp_from: 'alertmanager@example.org'CODE
LOWdocs/guides/alert-manager-configuration.md39 smtp_from: 'alertmanager@example.org'CODE
LOWdocs/api/_index.md877 smtp_from: 'youraddress@example.org'CODE
LOWdocs/api/_index.md885 - to: 'youraddress@example.org'CODE
LOWpkg/alertmanager/multitenant_test.go1137 smtp_from: 'youraddress@example.org'CODE
LOWpkg/alertmanager/multitenant_test.go1143 - to: 'youraddress@example.org'CODE
LOWpkg/alertmanager/multitenant_test.go1214 smtp_from: 'youraddress@example.org'CODE
LOWpkg/alertmanager/multitenant_test.go1220 - to: 'youraddress@example.org'CODE
LOWpkg/alertmanager/alertstore/local/store_test.go135 smtp_from: 'alertmanager@example.org'CODE
LOWpkg/storage/bucket/client_test.go43 "client_email": "test@test.com",CODE
AI Slop Vocabulary3 hits · 8 pts
SeverityFileLineSnippetContext
MEDIUMintegration/e2ecortex/client.go709// TODO: Upgrade to Alertmanager v0.20.0+ and utilize vendored structsCOMMENT
MEDIUMwebsite/package-lock.json1114 "resolved": "https://registry.npmjs.org/robust-predicates/-/robust-predicates-3.0.3.tgz",CODE
MEDIUMpkg/api/api.go249 // UI components lead to a large number of routes to support, utilize a path prefix insteadCOMMENT
Verbosity Indicators3 hits · 6 pts
SeverityFileLineSnippetContext
LOW⚡pkg/util/grpcclient/signing_handler_test.go168 // Step 2: Distributor redeployed with newKey; ingester still in transition.COMMENT
LOW⚡pkg/util/grpcclient/signing_handler_test.go173 // Step 3: Ingester redeployed with newKey only.COMMENT
LOWpkg/ingester/pushstream_security_test.go119 // Step 2: Attacker requests to write into "tenant-B"COMMENT
Synthetic Comment Markers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHGENAI_POLICY.md294. **Honour the DCO.** Your `Signed-off-by` line on each commit certifies the [Developer Certificate of Origin](https://CODE