AI Slop Code Risk Monitor

readysettech/readyset

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

Readyset is a MySQL and Postgres wire-compatible caching layer that sits in front of existing databases to speed up queries and horizontally scale read throughput. Under the hood, ReadySet caches the results of cached select statements and incrementally updates these results over time as the underlying data changes.

2.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for readysettech/readyset, a Rust project with 5,299 GitHub stars. SynthScan examined 538,559 lines of code across 1161 source files, recording 1402 pattern matches distributed across 12 syntactic categories. The legacy adjusted pattern signal is 2.8 (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.8
Adjusted Signal
2.8
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
5.3K
Stars
Rust
Language
538.6K
Lines of Code
1.2K
Files
1.4K
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.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 1.5/100 · LOW

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

PR Review Velocity Impact 13.2/100 · LOW

Which changes need focused human review? 1402 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 0HIGH 1MEDIUM 62LOW 1339

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 1402 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 Block1303 hits · 1257 pts
SeverityFileLineSnippetContext
LOWdeny.toml1# This template contains all of the possible sections and their default valuesCOMMENT
LOWdeny.toml21yanked = "warn"COMMENT
LOWdeny.toml41 # arrow-ipc (through 59.x, used by datafusion through 55.x) require zstd ^0.13. NeitherCOMMENT
LOWdeny.toml81# The confidence threshold for detecting a license from license text.COMMENT
LOWdeny.toml101# The SPDX expression for the license requirements of the crateCOMMENT
LOWdeny.toml121# not have its license(s) checkedCOMMENT
LOWdeny.toml141allow = [COMMENT
LOWrustfmt.toml1edition = "2021"COMMENT
LOWreadyset-multiplex/src/lib.rs1//! Minimal multiplexed request/response transport for tower services.COMMENT
LOWreadyset-multiplex/src/lib.rs41/// [`finish_tag`](Self::finish_tag) once per inbound response.COMMENT
LOWreadyset-multiplex/src/lib.rs61 TransportFull,COMMENT
LOWreadyset-multiplex/src/server.rs21use crate::BoxError;COMMENT
LOWreadyset-adapter/src/backend.rs1//!COMMENT
LOWreadyset-adapter/src/backend.rs21//!COMMENT
LOWreadyset-adapter/src/backend.rs41//! STATEMENT` are called. It is also the only available option when a upstream fallback is notCOMMENT
LOWreadyset-adapter/src/backend.rs321/// (today: MySQL `caching_sha2_password` fast-auth digests) can be kept in sync.COMMENT
LOWreadyset-adapter/src/backend.rs461 /// the cache may still hold a pre-write value (TTL not yet expired, refresh not yetCOMMENT
LOWreadyset-adapter/src/backend.rs1041 /// Socket of the connected client.COMMENT
LOWreadyset-adapter/src/backend.rs1061 /// A cache of queries that we've seen, and their current state, used for processingCOMMENT
LOWreadyset-adapter/src/backend.rs1081 connections: Option<Arc<SkipSet<ConnectionInfo>>>,COMMENT
LOWreadyset-adapter/src/backend.rs1101 /// registry: owns the per-cache scoped descriptors and theCOMMENT
LOWreadyset-adapter/src/backend.rs1581 /// Specifies the default TTL for shallow caches when no TTL is specified.COMMENT
LOWreadyset-adapter/src/rls_coordinator.rs1//! Adapter-side coordinator that bridges the generic shallow cache to the RLS catalog.COMMENT
LOWreadyset-adapter/src/upstream_database.rs101 QueryDestination::UpstreamCOMMENT
LOWreadyset-adapter/src/upstream_database.rs241 /// associated with statement IDs, as long as after calling `on_prepare` on one instance of anCOMMENT
LOWreadyset-adapter/src/upstream_database.rs281 &'a mut self,COMMENT
LOWreadyset-adapter/src/query_status_cache.rs41/// cache filter will remember. When this is exceeded the map is bulk-clearedCOMMENT
LOWreadyset-adapter/src/query_status_cache.rs61 /// `id_to_status` shard lock, never the other way around. No path holds an `id_to_status`COMMENT
LOWreadyset-adapter/src/query_status_cache.rs81 /// has rejected to the reason for the rejection. Consulted byCOMMENT
LOWreadyset-adapter/src/query_status_cache.rs101 /// schema change can move it. Such a change also takes the status of every deep cache overCOMMENT
LOWreadyset-adapter/src/query_status_cache.rs121 /// Caches whose statement names a relation the catalog has not caught up to. Retried on theCOMMENT
LOWreadyset-adapter/src/query_status_cache.rs141}COMMENT
LOWreadyset-adapter/src/query_status_cache.rs901 (id, query_state.map(|s| s.value().migration_state.clone()))COMMENT
LOWreadyset-adapter/src/session_context.rs21/// Per-Postgres-connection security context.COMMENT
LOWreadyset-adapter/src/session_context.rs41 /// `current_user` per Postgres semantics. Only `SET SESSION AUTHORIZATION` writes both this andCOMMENT
LOWreadyset-adapter/src/session_context.rs61 /// True when the current `effective_role` / `bypass_rls` came from a transaction-local roleCOMMENT
LOWreadyset-adapter/src/session_context.rs321 pub fn bypass_rls(&self) -> bool {COMMENT
LOWreadyset-adapter/src/cache_acl.rs1//! Per-cache authorization state (the cache ACL, REA-6708).COMMENT
LOWreadyset-adapter/src/cache_acl.rs201 /// password).COMMENT
LOWreadyset-adapter/src/cache_acl_worker.rs1//! The cache-ACL freshness worker (REA-6708).COMMENT
LOWreadyset-adapter/src/cache_acl_worker.rs301 fingerprints: HashMap<Scope, (u64, Instant)>,COMMENT
LOWreadyset-adapter/src/session_mutation.rs1//! Recognise prepared statements that mutate per-connection session state, and apply the mutationCOMMENT
LOWreadyset-adapter/src/session_mutation.rs41}COMMENT
LOWreadyset-adapter/src/mcp_http.rs1//! Embedded MCP HTTP server.COMMENT
LOWreadyset-adapter/src/mcp_http.rs41#[derive(Debug)]COMMENT
LOWreadyset-adapter/src/mcp_http.rs301/// The endpoint only accepts the methods on an allowlist; unknown methods areCOMMENT
LOWreadyset-adapter/src/sampler.rs1//! Query SamplerCOMMENT
LOWreadyset-adapter/src/sampler.rs21//! raw bytes, and other types, avoiding cross-type collisions.COMMENT
LOWreadyset-adapter/src/shallow_key.rs1//! The adapter-side cache key for shallow caches.COMMENT
LOWreadyset-adapter/src/shallow_key.rs21/// `Ord` provides the canonical ordering [`SessionInputValues`] keeps its contents in.COMMENT
LOWreadyset-adapter/src/query_handler.rs21/// MySQL's `time_zone` session variable can be set to:COMMENT
LOWreadyset-adapter/src/query_handler.rs41 #[inline]COMMENT
LOWreadyset-adapter/src/query_handler.rs121/// How we should be handling a SQL `SET` statement.COMMENT
LOWreadyset-adapter/src/query_handler.rs301 /// Whether or not a given query requires fallback.COMMENT
LOWreadyset-adapter/src/utils.rs61/// Example:COMMENT
LOWreadyset-adapter/src/backend/prepared.rs121 /// The current ReadySet migration stateCOMMENT
LOWreadyset-adapter/src/backend/prepared.rs1101 // Capture the serve seams' staged decline before do_prepare's ownCOMMENT
LOWreadyset-adapter/src/backend/prepared.rs1301 true,COMMENT
LOWreadyset-adapter/src/backend/noria_connector.rs121 /// not exist in dataflow. This variant is not useful without an upstream connection.COMMENT
LOWreadyset-adapter/src/backend/noria_connector.rs261 /// Global and thread-local cache of view endpoints and prepared statements.COMMENT
1243 more matches not shown…
Decorative Section Separators52 hits · 164 pts
SeverityFileLineSnippetContext
MEDIUMtest-utils/proc-macros/src/lib.rs78// ── Structured upstream parsing ──────────────────────────────────────────COMMENT
MEDIUM⚡readyset-dataflow/src/domain/remapped_keys.rs18//! ┌─────────┐ ┌─────────┐COMMENT
MEDIUM⚡readyset-dataflow/src/domain/remapped_keys.rs22//! └─────────┘ └─────────┘COMMENT
MEDIUM⚡readyset-dataflow/src/domain/remapped_keys.rs26//! ┌─────────────────────────┐COMMENT
MEDIUM⚡readyset-dataflow/src/domain/remapped_keys.rs33//! └─────────────────────────┘COMMENT
MEDIUM⚡readyset-dataflow/src/domain/remapped_keys.rs37//! ─────────────COMMENT
MEDIUMreadyset-dataflow/src/domain/remapped_keys.rs49//! ──────────────COMMENT
MEDIUMreadyset-sql-passes/src/inline_leading_derived_table.rs1491 // ─── Coverage gap tests ────────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/lateral_join.rs866 // ── SELECT‑list COALESCE mapping policy for LATERAL lone‑aggregate (COUNT) ─────────────COMMENT
MEDIUMreadyset-sql-passes/src/unnest_subqueries.rs1333 // ── MATERIALIZE DERIVED TABLE & (EXISTS-only) PROBE SHAPING ────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/unnest_subqueries.rs2199 // ── Single‑valued RHS handling in WHERE (Scalar and non‑negated IN) ───────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs91// ─── Visitor ────────────────────────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs119// ─── Supported join operators ────────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs141// ─── No aggregates in WHERE ─────────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs154// ─── No nested aggregates ──────────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs215// ─── No aggregates in JOIN ON ──────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs239// ─── No duplicate FROM aliases ──────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs255// ─── GROUP BY semantic validation ───────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs513// ─── No duplicate derived-table column names ────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/validate_query_semantics.rs1217 // ─── Coverage gap tests ────────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/tests/rewrite_joins_tests.rs32// ─── Test helpers ─────────────────────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/tests/rewrite_joins_tests.rs68// ─── Group 1: Operator identity preservation ──────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/tests/rewrite_joins_tests.rs129// ─── Group 2: WHERE → SJ ON predicate routing ────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/tests/rewrite_joins_tests.rs218// ─── Group 3: Barrier semantics and segment-level reordering ──────────────────COMMENT
MEDIUMreadyset-sql-passes/src/tests/rewrite_joins_tests.rs396// ─── Group 4: Hoisting exclusion ──────────────────────────────────────────────COMMENT
MEDIUMreadyset-sql-passes/src/tests/rewrite_joins_tests.rs444// ─── Coverage gap tests ────────────────────────────────────────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3273// ─── LHS subquery with WHERE into LEFT JOIN ────────────────────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3321// ─── Redundant DISTINCT stripping (ExactlyOne / AtMostOne) ─────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3338// ─── Regression guards for LHS+WHERE relaxation ────────────────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3401// ─── Deeply disguised ExactlyOne DISTINCT stripping ────────────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3485// ─── Per-level subquery guard regression tests ─────────────────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3555// ─── Correlated subqueries inside inlinables ───────────────────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3634// ─── Item 6: RHS LEFT JOIN inlining with WHERE → ON absorption ─────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3705// ─── Item 7: NULL promotion → inlining interaction ─────────────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3745// ─── Item 8: Aggregated subquery inlining path ─────────────────────────────COMMENT
MEDIUM…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3815// ─── Numeric GROUP BY resolution during inlining ─────────────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs36// ─── Test helpers ─────────────────────────────────────────────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs173// ─── Group 2: All-or-nothing — filters must not stop midway ───────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs231// ─── Group 3: Hoisting barriers — LEFT/RIGHT/FULL JOIN ────────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs264// ─── Group 4: Hoisting barriers — aggregation ─────────────────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs333// ─── Group 5: Hoisting barriers — window functions ────────────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs369// ─── Group 6: ON → WHERE promotion (INNER JOIN only) ─────────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs394// ─── Group 7: HAVING → WHERE promotion (group-key filters) ────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs445// ─── Group 8: Idempotency / no duplicates ─────────────────────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs486// ─── Group 9: Correct alias qualification ─────────────────────────────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs503// ─── Group 10: Multiple conjuncts — partial hoisting within WHERE ──────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs526// ─── Group 11: INNER JOIN subquery — filter hoisted, LEFT JOIN — not ──────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs554// ─── Group 12: sub_locals guard (M3 fix) + CROSS JOIN barrier ──────────────COMMENT
MEDIUM…passes/src/tests/hoist_parametrizable_filters_tests.rs591// ─── Negative tests: filters that must NOT be hoisted ──────────────────────COMMENT
MEDIUMreplicators/src/postgres_connector/connector.rs1410 // ── accumulate_row ──────────────────────────────────────────────COMMENT
MEDIUMreplicators/src/postgres_connector/connector.rs1476 // ── flush ───────────────────────────────────────────────────────COMMENT
MEDIUMreplicators/src/postgres_connector/connector.rs1525 // ── advance / should_flush / reset_window ──────────────────────COMMENT
AI Slop Vocabulary10 hits · 26 pts
SeverityFileLineSnippetContext
MEDIUMquery-generator/src/lib.rs342 // of the fk. This isn't super robust (unsurprisingly) and should probably beCOMMENT
LOWreadyset-e2e-tests/Cargo.toml75# In a test crate, we are ok with todo!(); could remove them and just use workspace lintsCOMMENT
LOWreadyset-logictest/Cargo.toml77# In a test crate, we are ok with todo!(); could remove them and just use workspace lintsCOMMENT
MEDIUMreadyset-dataflow/src/ops/grouped/aggregate.rs348// Could look into refactoring / creating a more robust testing infrastructure to consolidateCOMMENT
MEDIUMdataflow-state/src/persistent_state/mod.rs1568// Essentially we have to implement a huge hack here, since the only way I could findCOMMENT
LOWreadyset-sql/Cargo.toml40# During initial development, we are ok with todo!(); could remove them and just use workspace lintsCOMMENT
MEDIUMreplication-offset/src/postgres.rs17/// the LSNs of **COMMIT** events we receive will monotonically increase. We leverage this byCOMMENT
MEDIUMreadyset-sql-passes/src/rewrite_utils.rs3332 // Required keys should be columns by precondition; keep shape robust.COMMENT
MEDIUMnom-sql-arbitrary/src/expression/expr.rs18/// Essentially, this defines the type of the [`Expr`] and which values it will use when generatingCOMMENT
MEDIUMreplicators/src/noria_adapter.rs788 // attached. This is more robust than locking and allows us to reuseCOMMENT
Verbosity Indicators10 hits · 21 pts
SeverityFileLineSnippetContext
LOW⚡readyset-shallow/src/cache.rs1673 // Step 1: First registration → version 1.COMMENT
LOW⚡readyset-shallow/src/cache.rs1682 // Step 2: Simulate eviction — remove from active_keys.COMMENT
LOW⚡readyset-shallow/src/cache.rs1688 // Step 3: New miss re-registers K → version 2.COMMENT
LOW⚡readyset-shallow/src/cache.rs1697 // Step 4: Simulate the batched reschedule that process_due_callbacksCOMMENT
LOW⚡readyset-sql-passes/src/normalize_subquery_positions.rs741 // Step 1: LHS/outer-level rebind via unified top-down walk.COMMENT
LOW⚡readyset-sql-passes/src/normalize_subquery_positions.rs749 // Step 2: subquery-body correlation rebind. Generic outermost-SELECTCOMMENT
LOW⚡…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3716 // Step 1: NULL promotion — WHERE t2.b > 0 null-rejects t2 → LEFT → INNERCOMMENT
LOW⚡…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3717 // Step 2: LHS subquery with multi-table (t1 JOIN t3): first join is nowCOMMENT
LOWreadyset-server/src/controller/mir_to_flow.rs1182 // we need to check if the rhs parent is fully materialized, as this is needed for straddled joinCOMMENT
LOWreadyset-server/src/controller/mir_to_flow.rs1339 // we need to check if the rhs parent is fully materialized, as this is needed for straddled joinCOMMENT
Structural Annotation Overuse9 hits · 20 pts
SeverityFileLineSnippetContext
LOW⚡readyset-shallow/src/cache.rs1673 // Step 1: First registration → version 1.COMMENT
LOW⚡readyset-shallow/src/cache.rs1682 // Step 2: Simulate eviction — remove from active_keys.COMMENT
LOW⚡readyset-shallow/src/cache.rs1688 // Step 3: New miss re-registers K → version 2.COMMENT
LOW⚡readyset-shallow/src/cache.rs1697 // Step 4: Simulate the batched reschedule that process_due_callbacksCOMMENT
LOWreadyset-dataflow/src/ops/join.rs1394 // NOTE: This function relies pretty heavily on the fact that upqueries for NULLs are notCOMMENT
LOW⚡readyset-sql-passes/src/normalize_subquery_positions.rs741 // Step 1: LHS/outer-level rebind via unified top-down walk.COMMENT
LOW⚡readyset-sql-passes/src/normalize_subquery_positions.rs749 // Step 2: subquery-body correlation rebind. Generic outermost-SELECTCOMMENT
LOW⚡…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3716 // Step 1: NULL promotion — WHERE t2.b > 0 null-rejects t2 → LEFT → INNERCOMMENT
LOW⚡…t-sql-passes/src/tests/derived_tables_rewrite_tests.rs3717 // Step 2: LHS subquery with multi-table (t1 JOIN t3): first join is nowCOMMENT
Redundant / Tautological Comments7 hits · 10 pts
SeverityFileLineSnippetContext
LOWquickstart/readyset_demo.sh88 # Print resultsCOMMENT
LOWquickstart/check_db_size.sh29 # Check if user has the "@" signal - empty passwordCOMMENT
LOWquickstart/check_db_size.sh34 # Check if password is emptyCOMMENT
LOWquickstart/check_db_postgres.sh34 # Check if user has the "@" signal - empty passwordCOMMENT
LOWquickstart/check_db_postgres.sh39 # Check if password is emptyCOMMENT
LOWquickstart/check_db_postgres.sh78 # Check if AWS CLI is configuredCOMMENT
LOWquickstart/check_db_postgres.sh252 # Check if superuserCOMMENT
Self-Referential Comments3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUM.buildkite/pipeline.public-common.yml1# This file contains common build steps that can be included in other pipeline contexts.COMMENT
MEDIUM.buildkite/pipeline.yml1# This file contains steps for running the public OSS pipeline. It definesCOMMENT
MEDIUM.buildkite/push_docker_image_manifest.sh38# Create a new array in which each architecture in the archs array is prefixed with the image tagCOMMENT
AI Response Leakage1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHproptest-stateful/src/lib.rs176 /// standpoint, so that is all that I've implemented for now. Designing and implementing aCOMMENT
Fake / Example Data4 hits · 4 pts
SeverityFileLineSnippetContext
LOWreadyset-e2e-tests/tests/replica_identity.rs73 (1, 'John Doe', 'john@example.com'),CODE
LOWreadyset-e2e-tests/tests/replica_identity.rs74 (2, 'Jane Doe', 'jane@example.com'),CODE
LOWreadyset-e2e-tests/tests/replica_identity.rs122 assert_eq!(first_row_col(&rows, 1), "John Doe");CODE
LOWreplicators/benches/binlog_json.rs118 "name": "Jane Doe", "email": "jane@example.com", "country": "BR",CODE
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWreadyset-server/src/controller/state.rs2034/// # How to useCOMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…c/shallow/auto_cache_eligibility/gen_mysql_builtins.py138 except Exception as e: # noqa: BLE001 - supplementary source, docs is the baseCODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…c/shallow/auto_cache_eligibility/gen_mysql_builtins.py96CODE