Home / StackExchange / StackExchange.Redis
AI Slop Code RIsk Monitor

StackExchange/StackExchange.Redis

The Redis client for .NET

6.8 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for StackExchange/StackExchange.Redis, a C# project with 6,204 GitHub stars. SynthScan examined 194,316 lines of code across 901 source files, recording 910 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 6.8 (Moderate 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.

6.8
Adjusted Signal
6.8
Raw Pattern Score
100%
Time Factor
2026-10-10
Last Push
6.2K
Stars
C#
Language
194.3K
Lines of Code
901
Files
910
Pattern Hits
2026-10-12
Scan Date
0.06
HC Hit Rate

Risk Review · v3

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

Cognitive Ownership Risk 17.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 12.4/100 · LOW

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

Agent Over-Engineering Ratio 1.3/100 · LOW

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

PR Review Velocity Impact 29.4/100 · MEDIUM

Which changes need focused human review? 910 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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 43HIGH 10MEDIUM 2LOW 855

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 910 distinct pattern matches across 6 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 Block850 hits · 756 pts
SeverityFileLineSnippetContext
LOWeng/StackExchange.Redis.Build/Diagnostics.cs1using Microsoft.CodeAnalysis;COMMENT
LOWeng/StackExchange.Redis.Build/Diagnostics.cs21/// </para>COMMENT
LOWeng/StackExchange.Redis.Build/Diagnostics.cs41/// cref="DiagnosticSeverity.Error"/> in the set - which describes code that cannot work rather than code thatCOMMENT
LOWeng/StackExchange.Redis.Build/Diagnostics.cs81 /// Family B: a newer single command subsumes both the condition and the write.COMMENT
LOWeng/StackExchange.Redis.Build/Diagnostics.cs161COMMENT
LOWeng/StackExchange.Redis.Build/Diagnostics.cs201 /// <c>RedisTransaction.ExecuteAsync</c>), so this one is legal: it returns immediately, and the command isCOMMENT
LOWeng/StackExchange.Redis.Build/Diagnostics.cs221COMMENT
LOWeng/StackExchange.Redis.Build/Diagnostics.cs261 /// needs a thread of its own - but reached through the API the library itself offers for it, rather thanCOMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs1using System.Collections.Immutable;COMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs241 /// Where a call sits within the block: which branch of it, and whether it can run more than once.COMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs401 public string? Key { get; }COMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs421COMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs441 private List<ISymbol>? _conditionReads;COMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs661 _operations.Count.ToString(CultureInfo.InvariantCulture),COMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs701 "StringGet" => ("StringGet[Async](keys)", true, false, ServerVersion.Any, "key"),COMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs741 // -- family C: the write already reports what the condition was checking --COMMENT
LOWeng/StackExchange.Redis.Build/TransactionAnalyzer.cs761 // (HashFieldSet with ValueCondition.Exists, HSETEX FXX, 8.0+)COMMENT
LOWeng/StackExchange.Redis.Build/QueuedResultAnalyzer.cs1using System.Collections.Generic;COMMENT
LOWeng/StackExchange.Redis.Build/QueuedResultAnalyzer.cs21/// <para>COMMENT
LOWeng/StackExchange.Redis.Build/QueuedResultAnalyzer.cs101 // An ordinary redis call, already in flight: only *blocking* is a problem, and awaiting is exactlyCOMMENT
LOWeng/StackExchange.Redis.Build/RoslynShims.cs1using Microsoft.CodeAnalysis;COMMENT
LOWeng/StackExchange.Redis.Build/RoslynShims.cs21COMMENT
LOWeng/StackExchange.Redis.Build/AutoDatabaseGenerator.cs241 None = 0,COMMENT
LOW…xchange.Redis.CodeFixes/QueuedResultCodeFixProvider.cs21/// case, so they cannot drift without a deliberate decision.COMMENT
LOWtoys/MaintenanceWatch/Program.cs1using System;COMMENT
LOW…/StackExchange.Redis.Server/RedisServer.Maintenance.cs61 /// </summary>COMMENT
LOW…/StackExchange.Redis.Server/RedisServer.Maintenance.cs81 {COMMENT
LOW…/StackExchange.Redis.Server/RedisServer.Maintenance.cs101 /// <para>COMMENT
LOW…/StackExchange.Redis.Server/RedisServer.Maintenance.cs141 internal void OnMaintenanceOptIn() => Interlocked.Increment(ref _maintenanceOptIns);COMMENT
LOW…/StackExchange.Redis.Server/RedisServer.Maintenance.cs201 var delay = MovingCloseDelay ?? TimeSpan.FromSeconds(Math.Max(timeSeconds, 0)) + MeasuredCloseSlack;COMMENT
LOW…/StackExchange.Redis.Server/RedisServer.Maintenance.cs221 /// How much later than the announced window the close actually arrives, by default.COMMENT
LOW…/StackExchange.Redis.Server/RedisServer.Maintenance.cs281 /// <returns>The number of clients the notification was sent to.</returns>COMMENT
LOWtoys/StackExchange.Redis.Server/RedisServer.cs201 /// </summary>COMMENT
LOWtoys/StackExchange.Redis.Server/RedisServer.cs221 public enum AnnouncedAddressCOMMENT
LOWtoys/StackExchange.Redis.Server/RedisServer.cs341 /// Setting this afterwards, via <see cref="SetAnnouncedAddress"/>, leaves a window in which a topologyCOMMENT
LOWtoys/StackExchange.Redis.Server/RedisServer.cs401 /// Removes a node from the cluster entirely, as <c>CLUSTER FORGET</c> does: it stops appearing inCOMMENT
LOWtoys/StackExchange.Redis.Server/RedisServer.cs841 /// <summary>Reply with an error, as a server whose feature flag is off does.</summary>COMMENT
LOWtoys/StackExchange.Redis.Server/RedisServer.cs1201 public string Host { get; }COMMENT
LOWtoys/StackExchange.Redis.Server/RedisServer.cs1221 /// <summary>COMMENT
LOWtoys/StackExchange.Redis.Server/TypedRedisValue.cs1using System;COMMENT
LOWtoys/StackExchange.Redis.Server/TypedRedisValue.cs61COMMENT
LOWtests/StackExchange.Redis.Build.Tests/TestSetup.cs21 /// Test sources use string literals for keys/values, which trips the library's own <c>[Experimental]</c>COMMENT
LOWtests/StackExchange.Redis.Build.Tests/SER305.cs161 /// </summary>COMMENT
LOWtests/StackExchange.Redis.Build.Tests/Verifier.cs21 /// <summary>Expect a diagnostic with this id at the marked location.</summary>COMMENT
LOW…hange.Redis.Benchmarks/RedisValueEqualityBenchmarks.cs1using System;COMMENT
LOW…ckExchange.Redis.Benchmarks/MessageWriterBenchmarks.cs1using System;COMMENT
LOW…FaultInjector.Tests/ClusterWideFailureScenarioTests.cs1using System;COMMENT
LOW…FaultInjector.Tests/ClusterWideFailureScenarioTests.cs21/// client would come back, which it cannot do when there is nothing to come back to. What *is* assertable isCOMMENT
LOW…Exchange.Redis.FaultInjector.Tests/TestOutputWriter.cs1using System;COMMENT
LOW…dis.FaultInjector.Tests/TopologyChangeScenarioTests.cs61 {COMMENT
LOW…tackExchange.Redis.FaultInjector.Tests/AssemblyInfo.cs1using Xunit;COMMENT
LOW…nge.Redis.FaultInjector.Tests/MultiThreadedWorkload.cs1using System;COMMENT
LOW…nge.Redis.FaultInjector.Tests/MultiThreadedWorkload.cs41 // Task.Run rather than dedicated threads: the multiplexer is thread-agnostic, and the floor raisedCOMMENT
LOW…FaultInjector.Tests/MovingEndpointTypeScenarioTests.cs1using System;COMMENT
LOW…FaultInjector.Tests/MovingEndpointTypeScenarioTests.cs21/// skip the DNS wait entirely, and DNS has been measured trailing the notification by up to 18.7s against aCOMMENT
LOW…Redis.FaultInjector.Tests/RetentionAgeScenarioTests.cs21/// <c>MOVING</c>), delivered within ~17ms of the opt-in being accepted, most-recent-replaces. What is notCOMMENT
LOW…Redis.FaultInjector.Tests/RetentionAgeScenarioTests.cs41 /// Progress is written to a file as it happens, as well as to the test output.COMMENT
LOW…Redis.FaultInjector.Tests/RetentionAgeScenarioTests.cs221 /// </summary>COMMENT
LOW…dis.FaultInjector.Tests/AzureManagedRedisOptInTests.cs1using System;COMMENT
LOW….Redis.FaultInjector.Tests/DestructiveScenarioTests.cs21/// this feature adds - relaxed windows, handoffs, endpoint retirement - sits on top of ordinary reconnect andCOMMENT
790 more matches not shown…
Hallucination Indicators43 hits · 508 pts
SeverityFileLineSnippetContext
CRITICALtests/StackExchange.Redis.Tests/GlobalSuppressions.cs13[assembly: SuppressMessage("Usage", "xUnit1004:Test methods should not be skipped", Justification = "Pending", Scope = "CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt57StackExchange.Redis.Availability.CircuitBreaker.Accumulator.Accumulator() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt58virtual StackExchange.Redis.Availability.CircuitBreaker.Accumulator.IsFailure(in StackExchange.Redis.Availability.FaultCCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt59abstract StackExchange.Redis.Availability.CircuitBreaker.Accumulator.IsHealthy() -> boolCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt60abstract StackExchange.Redis.Availability.CircuitBreaker.Accumulator.ObserveResult(in StackExchange.Redis.Availability.FCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt61abstract StackExchange.Redis.Availability.CircuitBreaker.Accumulator.Reset() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt63StackExchange.Redis.Availability.CircuitBreaker.Builder.Builder() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt64StackExchange.Redis.Availability.CircuitBreaker.Builder.Create() -> StackExchange.Redis.Availability.CircuitBreaker!CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt121StackExchange.Redis.Availability.HealthCheck.Builder.Builder() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt122StackExchange.Redis.Availability.HealthCheck.Builder.Builder(StackExchange.Redis.Availability.HealthCheck! healthCheck) CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt123StackExchange.Redis.Availability.HealthCheck.Builder.Create() -> StackExchange.Redis.Availability.HealthCheck!CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt196StackExchange.Redis.Availability.MultiGroupOptions.Builder.Builder() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt197StackExchange.Redis.Availability.MultiGroupOptions.Builder.Builder(StackExchange.Redis.Availability.MultiGroupOptions! oCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt200StackExchange.Redis.Availability.MultiGroupOptions.Builder.Create() -> StackExchange.Redis.Availability.MultiGroupOptionCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt219StackExchange.Redis.Availability.RetryPolicy.Builder.Builder() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt220StackExchange.Redis.Availability.RetryPolicy.Builder.Builder(StackExchange.Redis.Availability.RetryPolicy! policy) -> voCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt221StackExchange.Redis.Availability.RetryPolicy.Builder.Create() -> StackExchange.Redis.Availability.RetryPolicy!CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt616override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.BeginRead(byte[]! buffer, int offset, int cCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt617override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.BeginWrite(byte[]! buffer, int offset, int CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt622override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.Close() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt623override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.EndRead(System.IAsyncResult! asyncResult) -CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt624override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.EndWrite(System.IAsyncResult! asyncResult) CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt625override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.Flush() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt626override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.FlushAsync(System.Threading.CancellationTokCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt630override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.Read(byte[]! buffer, int offset, int count)CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt631override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.ReadAsync(byte[]! buffer, int offset, int cCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt632override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.ReadByte() -> intCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt635override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.Seek(long offset, System.IO.SeekOrigin origCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt636override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.SetLength(long value) -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt637override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.Write(byte[]! buffer, int offset, int countCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt638override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.WriteAsync(byte[]! buffer, int offset, int CODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt639override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.WriteByte(byte value) -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt2329StackExchange.Redis.Profiling.ProfiledCommandEnumerable.Enumerator.Dispose() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt2330StackExchange.Redis.Profiling.ProfiledCommandEnumerable.Enumerator.Enumerator() -> voidCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt2331StackExchange.Redis.Profiling.ProfiledCommandEnumerable.Enumerator.MoveNext() -> boolCODE
CRITICAL⚡src/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt2332StackExchange.Redis.Profiling.ProfiledCommandEnumerable.Enumerator.Reset() -> voidCODE
CRITICALsrc/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt2784StackExchange.Redis.Role.Master.Replica.Replica() -> voidCODE
CRITICALsrc/StackExchange.Redis/PublicAPI/PublicAPI.Shipped.txt2786override StackExchange.Redis.Role.Master.Replica.ToString() -> string!CODE
CRITICAL⚡…kExchange.Redis/PublicAPI/net6.0/PublicAPI.Shipped.txt2override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.DisposeAsync() -> System.Threading.Tasks.VaCODE
CRITICAL⚡…kExchange.Redis/PublicAPI/net6.0/PublicAPI.Shipped.txt3override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.Read(System.Span<byte> buffer) -> intCODE
CRITICAL⚡…kExchange.Redis/PublicAPI/net6.0/PublicAPI.Shipped.txt4override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.ReadAsync(System.Memory<byte> buffer, SysteCODE
CRITICAL⚡…kExchange.Redis/PublicAPI/net6.0/PublicAPI.Shipped.txt5override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.Write(System.ReadOnlySpan<byte> buffer) -> CODE
CRITICAL⚡…kExchange.Redis/PublicAPI/net6.0/PublicAPI.Shipped.txt6override StackExchange.Redis.Configuration.LoggingTunnel.LoggingDuplexStream.WriteAsync(System.ReadOnlyMemory<byte> buffCODE
Cross-File Repetition10 hits · 50 pts
SeverityFileLineSnippetContext
HIGHtests/StackExchange.Redis.Build.Tests/SER306.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGHtests/StackExchange.Redis.Build.Tests/SER305CodeFix.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGHtests/StackExchange.Redis.Build.Tests/DetectionShape.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGHtests/StackExchange.Redis.Build.Tests/SER302.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGHtests/StackExchange.Redis.Build.Tests/SER303.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGHtests/StackExchange.Redis.Build.Tests/SER300.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGH…ts/StackExchange.Redis.Build.Tests/MinServerVersion.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGHtests/StackExchange.Redis.Build.Tests/SER304.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGHtests/StackExchange.Redis.Build.Tests/SER305.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
HIGHtests/StackExchange.Redis.Build.Tests/SER301.cs0using stackexchange.redis; using system.threading.tasks; class c { public async task m(idatabase db, rediskey key) { varSTRING
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUM…ultInjector.Tests/ActiveActiveFailoverScenarioTests.cs239 /// identity, more robust than Jedis's "first event = failover, second = failback") the first switch awayCOMMENT
MEDIUM…ts/StackExchange.Redis.Tests/GarbageCollectionTests.cs26 // this is more nuanced than it looks; multiple sockets withCOMMENT
Fake / Example Data4 hits · 6 pts
SeverityFileLineSnippetContext
LOW⚡tests/StackExchange.Redis.Tests/KeyTests.cs337 [InlineData(false, "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras lobortis quam ac molestie ultricieCODE
LOW⚡tests/StackExchange.Redis.Tests/KeyTests.cs337 [InlineData(false, "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras lobortis quam ac molestie ultricieCODE
LOW⚡tests/StackExchange.Redis.Tests/KeyTests.cs345 [InlineData(true, "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras lobortis quam ac molestie ultriciesCODE
LOW⚡tests/StackExchange.Redis.Tests/KeyTests.cs345 [InlineData(true, "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras lobortis quam ac molestie ultriciesCODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWeng/public-api.py77CODE