crbench//

Drape (Review)

Latest run 2026-11-11-s2 · model review

61%
Rating · High
95% 56%–66% · 1016 matchups
81.8%
Coverage
80.8%
Cross-File
33/37
Security
91% severity-weighted
98.9%
Validity
1.1%
False-alarms
127
Cases (100%)

Head-to-head — compare defect-by-defect

vs Claude Code (Opus 5.5)vs Cubicvs cursorvs Drape (Deep Review)vs greptilevs Mjolnir (Opus 5.5)vs Mjolnir (Sonnet 5.5)vs qodo

Coverage by severity — expand a row to see what it missed

critical 4/5 (80.0%)
maybeDoSizeFlush assigns `lastFile.Span.EndKey = newSpan.Key` without cloning, but newSpan.Key aliases the caller's reused scratch buffer in compactSpanEntry. The next WriteKey overwrites scratch in place, silently mutating the already-recorded EndKey and producing BackupManifest_File entries with overlapping/drifted spans (corrupted backup metadata). Sibling Reset paths in the same file clone correctly; maybeDoSizeFlush was missed.
high 92/108 (85.2%)
The diff switches worker creation from the default `multiprocessing.Process(...)` to `multiprocessing.get_context("spawn").Process(...)`, which reads as a sound fork-safety improvement. But the unchanged Reaper.reap() in reaper.py gates its kill on `isinstance(process, multiprocessing.Process)`. Spawn-context workers are SpawnProcess instances, and `multiprocessing.Process` is the generic context.Process — a sibling BaseProcess subclass, not a base of SpawnProcess — so the gate is now always False and reap() silently kills nothing, leaking stalled flushers. The change looks correct in isolation; the regression is only visible by reading the unchanged reaper and knowing that spawn-context processes fail the isinstance check.
scheduleSMS returns undefined on SMS-lock and throws on rate-limit/missing-creds; both paths increment retryCount, and the new deleteMany OR clause (retryCount > 1, with no method/date filter) permanently deletes those reminders after a few cron runs, so transient locks, monthly rate-limits, or a temporary Twilio misconfiguration silently drop reminders that previously stayed scheduled=false and were retried until scheduledDate.
The new date-override block is inserted ahead of the availability test that ends `checkIfIsAvailable` (`return busy.every(...)`). When a slot falls inside an override window the `find` callback sets `dateOverrideExist` and returns undefined, so `.find()` matches nothing, the outer branch is skipped, and `if (dateOverrideExist) return true` reports the slot bookable without ever evaluating `busy`. A slot inside a date override is offered even when it collides with an existing booking.
The new eventDecoder builds each event's row from `getPhysicalColumnsSchema`, which drops every computed column, stored ones included. When the crud writer applies a replicated delete for a row the destination does not have, the table handler passes that row to `tombstoneUpdater.updateTombstone`. The tombstone updater's row.Deleter is built from `writeableColunms`, which keeps stored computed columns, and indexes the row by position. On a table with a stored computed column, every later column's datum is shifted. For example, on `(k INT PRIMARY KEY, c INT AS (k+1) STORED, v INT, INDEX (v))` the Deleter reads `v` at ordinal 2 of a 2-element row, and secondary-index encoding panics with index out of range. A stored computed column ahead of a primary-key column shifts the primary-key datum in the same way.
The informer transform `trim` calls `accessor.SetManagedFields(nil)` unconditionally on every resync, mutating the object that lives in the shared informer cache. Because that cached object is read concurrently by other informer consumers, the unconditional in-place mutation is a data race that can panic kube-controller-manager / scheduler. The fix guards it (`if accessor.GetManagedFields() != nil`) so the transform is idempotent and does not rewrite shared state when already trimmed.
The new pod index `AddPodControllerUIDIndexer` / `PodControllerUIDIndex` keys solely on the owning controllerRef's UID (`[]string{string(ref.UID)}`), ignoring namespace, kind, and name. Controllers (DaemonSet/ReplicaSet/Job/StatefulSet) that look pods up through this index can claim the wrong pods when a stale or duplicated ownerReference UID collides. The fix re-keys the index on the full (namespace, kind, name, uid) tuple.
The new line `if (response.statusText !== "OK")` in salesforce CalendarService.getClient checks statusText, but Node's global fetch (undici) returns an empty statusText for HTTP/2 responses served by login.salesforce.com, so a successful 200 yields `"" !== "OK"` and throws HttpError on every Salesforce client construction.
This PR renames the private storage download/delete route from a single-segment [fileName] dynamic parameter to a catch-all [...filePath], specifically so it can also serve the newly introduced /storage/{workspaceId}/private/surveys/{surveyId}/elements/{elementId}/{file} scoped upload paths (per the PR's own description: "Scope new private upload URLs under .../surveys/{surveyId}/elements/{elementId}/..."). Both the nested route shape and the underlying storage key scheme for element-scoped uploads are new in this diff. Routing these newly introduced, more sensitive per-response upload files through the SAME entry point -- still gated only by the pre-existing, role-blind hasUserWorkspaceAccess (see d1) -- exposes them to billing-role users for the first time. This is a diff-attributable widening of exposure, distinct from d1's own (pre-existing, unchanged) check logic: unlike d1, this defect is genuinely introduced by the diff and should not be excluded from headline scoring.
In `prepareResources`, the branch that handles an already-prepared claim (`if claimInfo.isPrepared()`) does `return nil` instead of `continue`. Because this runs inside the `for ... range pod.Spec.ResourceClaims` loop, the first already-prepared claim short-circuits the whole loop and the pod's remaining ResourceClaims are never prepared. The fix changes `return nil` back to `continue`.
The response-handling refactor builds the /_next/data JSON page response as Buffer.from(JSON.stringify(result.value.pageData)). RenderResult.isDynamic decides static-vs-dynamic via `typeof this.response !== 'string'`, so a Buffer is misclassified as a dynamic stream; sendRenderResult then skips Content-Length and ETag and falls back to Transfer-Encoding: chunked, breaking CDN-side compression for self-hosted Pages Router deploys. The fix deletes the Buffer.from wrapper. (Large-diff stress case: ~3k lines, 22 files.)
With `trailingSlash: true`, the new handler templates (app-page.ts, app-route.ts, pages.ts) take `resolvedPathname` from the request URL, which base-server now rebuilds from the raw `initURL` and which still ends in a slash. None of them calls `removeTrailingSlash`, which base-server applied before its cache-key and prerender lookups. The build writes prerender-manifest keys without the slash, so every lookup misses. For app-page, a prerendered page on a `dynamicParams = false` route is taken to be unlisted and throws NoFallbackError (404), and the ISR cache key becomes `/blog/a/`, so the prebuilt output is never served.
The re-implemented Server Action reducer now rejects the action's promise with a redirect error for every redirect, external ones included, where it previously resolved them, and builds that error's URL with createHrefFromUrl, which keeps only the path and query, so an external URL loses its origin. Called from a form action or useTransition, React catches the handled error and the external navigation that handleExternalUrl staged (mpaNavigation) goes through. Called outside a React scope, such as a plain onClick, the rejection reaches the app router's unhandledrejection handler, which pushes the same-origin path; that navigation supersedes the external one, so the redirect to the external URL never happens.
In the new signals auto-start path (_resolve_autostart_assignee in products/signals/backend/auto_start.py), candidate users are filtered with User.objects.filter(..., teams__id=team_id). User.teams is a @cached_property on the User model, not an ORM relation, so this lookup raises Django FieldError ("Cannot resolve keyword 'teams' into field") every time the path reaches the query. The exception is swallowed upstream, so report generation keeps working but the auto-start path silently creates zero implementation tasks. It is cross-file because the teams cached_property lives in the user model file while the broken filter is in the changed auto_start.py code.
The change narrows shouldShowSyncColumns with `&& selectedConnector.supportsColumnSelection`, correct for column-selection but the same flag also gates the Sync-method, Sync-field, and Primary-key columns. supportsColumnSelection is false for all non-SQL sources (Stripe, Hubspot, REST), so those three controls silently disappeared for every non-SQL source during table setup.
A new usage-report query runs raw `FROM logs` through sync_execute() on the logs cluster. HogQL resolves its `logs` table to the physical `logs_distributed` table, and production's logs cluster has no table named `logs`: the `logs` Distributed table that migration 0214 creates exists only in local and test schemas, which is why the PR's test passes. In production the query fails, and since the new query runs unconditionally it aborts the whole usage-report run that feeds billing (reverted the next day in #60611).
In pkg/querier/postprocess.go the new prepareFillZeroArgsWithStep builds the fillZero function args as {req.Start, req.End, step} where step is computed in milliseconds (query.StepInterval.Duration.Milliseconds()) but req.Start/req.End are not guaranteed to be in milliseconds at runtime (callers may pass nanosecond-resolution timestamps). funcFillZero requires all three args in the same unit and loops from start to end by step appending one point per iteration; when start/end are nanoseconds and step is milliseconds the iteration count is ~10^6x too large, so the fill-zero path allocates an enormous slice of zero points and blows up memory / OOMs the query service.
medium 68/91 (74.7%)
Asynchronous functions deleteScheduledEmailReminder and deleteScheduledSMSReminder are called without await inside forEach loops. This occurs during booking rescheduling/cancellation, and workflow/workflow step deletion/updates. Consequently, scheduled workflow reminders may not be reliably cancelled, potentially leaving them active.
The new immediateDelete branch of deleteScheduledEmailReminder cancels the scheduled email at SendGrid on the spot, and three new call sites use it (rescheduling in handleNewBooking, workflow and workflow-step deletion in workflows.tsx). Each such cancellation stays pending in SendGrid's scheduled_sends until the email's send time, up to 72h ahead, and SendGrid allows only 100 pending cancellations: the limit this PR's deferred, cron-driven cancellation exists to stay under. Under steady rescheduling the immediate cancellations fill it, after which cancellations are rejected (and only logged), both the immediate ones and the cron's deferred ones, so reminders for rescheduled and cancelled bookings are sent anyway.
The new downsize loop tests `tempfile.size` and passes the same expression as the filesize argument to `Upload.create_for`, but the conversion ends in an image optimizer that atomically replaces the file. After the first pass the open Tempfile descriptor refers to an orphaned inode, so the reported size stops tracking the file on disk: the loop condition is frozen at the post-first-pass value and the upload is then rejected as too large by the validator even though the file has been shrunk well under the limit.
The cacher delegator's `GetList` adds an unconditional `if errors.IsResourceExpired(err) { return c.storage.GetList(...) }` fallback to etcd. When the cache snapshot is nil the cacher returns `ResourceExpired`, so consistent paginated LISTs silently fall back to etcd instead of being served from cache, defeating the feature and adding etcd load. The fix gates that fallback behind the cache-snapshot feature flag.
The rewritten reply builder uses one array for two incompatible purposes: a depth-indexed slot array written by index, and a LIFO stash for RESP3 map keys pushed and popped. When a map key is itself an aggregate, the push lands at the same index the slot write uses and the key's children grow the array, so the following value pops the key's last child instead of the key. The map is returned with a wrong key and no error is raised.
`checklist` is stored as a growing `v.array(...)` on the task document, so its size is bounded by Convex's 1 MB per-document limit rather than by anything in the code: once a task accumulates enough items the patch in `addItem` fails and the task can no longer be written. Every toggle also rewrites the whole array, so write cost grows with the item count, and individual items cannot be indexed or queried. The fix is a separate `checklistItems` table keyed by `taskId`. Stated as the document-size limit rather than as a design preference, because that is the hard ceiling that makes writes fail and is what expectations.md records as the pass condition ("risks hitting the 1MB document size limit").
`toggleItem` declares `index: v.number()`, which accepts any float and NaN, and guards with `if (args.index < 0 || args.index >= checklist.length)`. Both comparisons are false for NaN, and 0.5 sits inside the range, so the guard passes, `checklist[args.index]` is `undefined`, and reading `.completed` off it throws an unhandled TypeError. Reachable from the public mutation API, which is what the validator exists to constrain.
Backup code validation is case-sensitive due to the use of indexOf(). This causes validation to fail if a user enters uppercase hex characters, as backup codes should be case-insensitive for a better user experience.
The diff converts the outer cancellation lookup from `find` to `filter` and loops over every calendar reference, but the recurring branch still resolves a single reference with `references.find((ref) => ref.type.includes('_calendar'))` and iterates only the organizer's credentials. For each remaining occurrence only the first reference is deleted and only with the organizer's credentials, so team members' calendar events survive the cancellation.
The new image-set loader offers a "Pad" resize option whose branch is identical to "Stretch": it calls the same full resize to the target width and height, with no aspect-preserving thumbnail and no border fill. A user who loads a folder of differently sized images and picks "Pad" to keep aspect ratio gets every image whose size differs from the first one non-uniformly squashed, silently corrupting the training data, with nothing reporting that the chosen option behaved the same as "Stretch".
`remove_member` deletes the association with `group.users.delete(user_id)`, which for a has_many-through with no `:dependent` resolves to a raw `delete_all` and never instantiates the join model, so the `counter_cache` on GroupUser never decrements. The sibling add path uses `group.add(user)`, which does instantiate and increments, so `groups.user_count` drifts upward monotonically and is rendered to admins and returned by the group endpoint.
`TestNewClaimInfoFromClaim` and `TestNewClaimInfoFromState` assert with an inverted condition: `if reflect.DeepEqual(result, test.expectedResult) { t.Errorf(...) }`. That reports a failure only when the result MATCHES the expectation, so the tests never validate the constructor and pass vacuously (and `expectedResult` is left nil). The fix inverts the check to `if !reflect.DeepEqual(...)`.
The claimInfo-cache tests seed their "item in cache" fixtures under the key `claimName + namespace`, but the cache itself keys entries on `namespace + "/" + claimName`. The mismatched key means the seeded entry is never found, so the `get`/`delete`/`contains` tests pass vacuously without exercising the real lookup. The fix keys the fixtures on `namespace + "/" + claimName` to match the cache.
In verifySafeHtml the prefix length `start` and suffix length `end` are computed independently with no `start+end <= value.length()` guard, so when the OWASP sanitizer balances mis-nested allowed tags (e.g. `<p><b>x</p>` → `<p><b>x</b></p>`) the overlapping prefix/suffix make `value.substring(start, value.length()-end)` have beginIndex > endIndex, throwing StringIndexOutOfBoundsException exactly on the illegal-HTML case it should report.
ConditionalPasskeysEnabled() called without UserModel parameter
The new source-action code generators emit commands with a hardcoded `nbls.`-prefixed name (e.g. `new Command(..., "nbls.generate.code", ...)`) instead of routing the name through `Utils.encodeCommand(command, client.getNbCodeCapabilities())` the way the sibling generators do. Any LSP client whose capabilities use a different command prefix gets a dead source-action menu. The fix runs the command name through `encodeCommand` so it respects the client's prefix.
The pages template sets `isIsrFallback` for an ungenerated path of a `fallback: true` route and clears it only for bots, minimal mode or an existing cache entry, never for on-demand revalidation. Base-server forced a blocking render when `isOnDemandRevalidate` was set. So `res.revalidate('/posts/new')` for a path not yet generated now returns the build-time fallback shell with its cache control deleted: nothing is stored, yet the response carries `x-nextjs-cache: REVALIDATED`, so the revalidate call reports success without generating the page.
The app-page template adds an early `if (isSSG && prerenderInfo?.fallback === false && !isPrerendered) throw new NoFallbackError()` that runs before draft mode or minimal mode is considered. The base-server check it replaces skipped preview/draft mode and minimal mode, and the sibling pages and app-route templates keep a `!isDraftMode` guard. A draft-mode request for a path of a `dynamicParams = false` app page that was not prerendered now returns 404 instead of rendering on demand, which breaks CMS preview of unpublished pages.
In applyFormulas (pkg/querier/postprocess.go), the new RequestTypeScalar branch calls applySeriesLimit on the result of processScalarFormula, but that result's Value is a *qbtypes.ScalarData while applySeriesLimit type-asserts result.Value.(*qbtypes.TimeSeriesData) and returns the result unchanged when the assertion fails. So for scalar/formula query results the call is effectively dead code: the configured order-by and limit on the formula are silently ignored, and scalar formula results come back unordered with no limit applied.
In VisitComparison's IN-clause branch, `case []any: values = varValues` passes an empty slice straight through when a variable resolves to []any{}. condition_builder.go's FilterOperatorIn handler then builds conditions := []string{} from an empty values, and sb.Or(conditions...) with zero arguments returns an empty string (confirmed in the vendored huandu/go-sqlbuilder@v1.35.0 source: Or returns "" when len(orExpr) == 0 after filtering). The generated WHERE-clause fragment for that condition vanishes rather than encoding "no rows match", so a filter meant to exclude everything silently matches all rows instead.
chSQLQuery.renderVars substitutes variable values into the raw ClickHouse query string via strings.Replace BEFORE parsing that string as a Go text/template (tmpl.Parse(query) / tmpl.Execute). If a variable's own VALUE contains the Go template delimiters {{/}}, the substituted text is then re-interpreted as a live template action in the second stage -- e.g. a variable value of "{{.SIGNOZ_START_TIME}}" gets replaced with the numeric start timestamp rather than being treated as literal text, silently changing the rendered query; a malformed template fragment (e.g. "{{.") causes template.Parse to fail, surfacing as an opaque HTTP 500.
parseFieldKeyRequest renames the field-key search parameter from ?name to ?searchText (r.URL.Query().Get("name") -> r.URL.Query().Get("searchText")). parseFieldValueRequest calls parseFieldKeyRequest internally (now reading ?searchText) and separately reads ?name for a different purpose (keySelector.Name, overriding what the key-request set). Any existing caller using GET /api/v1/fields?name=service_name to filter the field-key list gets back all keys instead of a filtered set -- the ?name parameter is simply ignored for that endpoint, a breaking API change with no version bump.
rewriteExpression replaces all quoted string literals in the HAVING expression with __QUOTED_N__ placeholders BEFORE matching column-map keys against it. A key like countIf(level='error') (itself containing a quoted literal) is turned into a regex built from its raw, unprotected form, so it can never match the already-placeholder-substituted expression -- e.g. a HAVING clause countIf(level='error') > 10 reads as countIf(level=__QUOTED_0__) > 10 after quote-protection, and the \bcountIf\(level='error'\) pattern silently fails to match, so the rewrite (and the __result_N substitution downstream code depends on) is silently skipped.
low 25/32 (78.1%)
uniqueGuests filters out existing attendees and blacklisted emails but does not deduplicate duplicates within the input; createMany can insert duplicate attendee rows if the client submits repeated emails.
logic: macOS-specific sed syntax with empty string after -i flag will fail on Linux systems
The test comment says the cached permissions 'allow access', but the map stores false for dashboards:uid:dash1, so checkPermission will still treat this scope as not allowed.
Breaking out of the loop when the deadline has elapsed can skip terminating remaining flusher processes, potentially leaving them running after shutdown; consider ensuring termination is attempted even if the deadline is exceeded.
With upsampling applied, events-stats sends the literal column `upsampled_count() as count` to the query builder. When the client also sets transformAliasToInputFormat=1, the builder's process_results renames the result key to that full input string, while the serializer looks up `count()` (resolve_axis_column returns the raw y-axis). `r.get(column, 0)` then finds nothing, so every bucket of the time series comes back as 0.
The app-page template's responseGenerator copies base-server's static-shell-debugging short-circuit, which returns a cache entry of `kind: CachedRouteKind.PAGES`. The template's own handleResponse then throws "Invariant app-page handler received invalid cache entry PAGES" for any kind other than APP_PAGE. Base-server served that entry through its generic branch as an empty HTML response, so a static-shell debugging request now fails with the invariant error.
The span bar position is computed with a CSS clamp: `left: clamp(0%, ${toPercent(bounds.left || 0)}, calc(100% - 1px))`. clamp floors the value at 0%, but when the view is zoomed via the minimap a span that starts before the visible window has a legitimately negative left; flooring it to 0% mis-positions the bar. The fix uses min(...) (no lower bound) so negative offsets render correctly.

By diff size — compare every bot

Pulls ahead on large diffs

The gap moves +10 pts from small to large, so it drops off less than the other bots do as PRs grow.

Diff sizeCasesBugs caughtCoverageOther bots, same PRsvs othersFalse-alarms
small ≤100 lines 54 59/64 92% 86% +6 pts 1%
medium 101–500 lines 40 57/74 81% 72% +9 pts 1%
large >500 lines 33 73/98 74% 58% +16 pts 1%

Every bot catches less as PRs grow, so a falling coverage number is expected. The question is whether this bot falls more or less than the others. vs others is its coverage minus what the other bots caught on the exact same PRs. The label compares that gap on small PRs with the gap on large ones; it takes a 10-point move to count. Coverage is severity-weighted: a critical bug counts 8×, a low one 1×.

Review time

Median 2.7 min and 90th percentile 5.3 min over 127 reviews.

Diff sizeReviewsMedian90th percentile
small ≤100 lines541.2 min2.7 min
medium 101–500 lines403.4 min5.5 min
large >500 lines334.7 min7.8 min

Timed from the start of the review to its end, run on our machine two at a time, so it has no queue to wait in. Times measured this way and a hosted bot's are not strictly comparable. See methodology.

Trajectory — coverage over time

RunCoverageValidityCases
2026-11-04-s188.0%98.9%81
2026-11-05-s173.9%98.4%46
2026-11-05-s280.8%98.2%127
2026-11-10-s175.5%97.1%30
2026-11-11-s182.7%98.8%97
2026-11-11-s270.2%98.5%56

Cases reviewed

Authored · Tier 1 · found 38/39 · 36 cases

CaseFoundFindingsFalse-alarms
A new required TRACKER_GEOCODER_URL setting is not added to the Helm chart, so every pod fails at startup 1/1 4 0
A new required TRACKER_GEOCODER_URL setting is not added to the Helm chart, so every pod fails at startup 1/1 4 0
Binary-sink migration missed an unchanged Serializer implementer (CsvSerializer still returns str) 1/1 1 0
Binding the tenant scope with `let _ =` drops the guard at once, so the digest reads every tenant's rows 1/1 1 0
Day-bucketing the keyset filter in the session timezone diverges from the UTC-pinned cursor and empties page 2 1/1 2 0
Environment scoping added to create/update but not the sibling delete leaves a cross-env IDOR 2/2 4 0
Filtering empty entries silently misaligns audit's positional entry/timestamp pairing 2/2 2 0
Handlers are now built once per context instead of per event, so the PayoutFees the fee schedule keeps for each payout.paid handler, which charges each seller once, stops charging the payout fee after a seller's first payout 1/1 1 0
Handlers are now built once per context instead of per event, so the PayoutFees the fee schedule keeps for each payout.paid handler, which charges each seller once, stops charging the payout fee after a seller's first payout 1/1 1 0
Lowercasing tags silently breaks the case-sensitive admin check in access.py 1/1 1 0
Moving the Server Action redirect into the render commit drops it on the unchanged non-React result path 2/2 3 1
Narrowing a shared visibility gate for one control silently hides two unrelated controls 1/1 1 0
Rejecting a zero throttle interval silently stops an unthrottled heartbeat that must always fire 1/1 1 0
Reordering Job's fields silently re-ranks the unchanged scheduler's heap by name instead of priority 1/1 1 0
Reusing a scratch buffer for end keys corrupts every recorded span via the retaining writer 1/1 1 0
Routing Amex to the legacy gateway breaks payments via an unchanged capability the diff can't see 1/1 1 0
Sorting the roster silently misaligns payroll's positional name/amount pairing 1/1 2 0
Stripping the trailing slash silently malforms URLs built by the unchanged helper 1/1 1 0
Switching encode() to chunks_exact silently discards the partial final frame of every batch 1/1 2 0
Switching flusher workers to the spawn context silently disables the reaper's isinstance-gated kill 0/1 1 0
The cached shipment payload changes shape without bumping CACHE_VERSION, so old entries are read as current 1/1 1 0
The cached shipment payload changes shape without bumping CACHE_VERSION, so old entries are read as current 1/1 1 0
The location record gains a field but the TypeScript client decoder keeps the old record layout 1/1 2 0
The location record gains a field but the TypeScript client decoder keeps the old record layout 1/1 2 0
check now sees each family's canonical values, and for an EDI line canonical() sets the quantity in units through units(), so Pinecrest's cap on the quantity as ordered rejects every case line over 150 units 1/1 1 0
check now sees each family's canonical values, and for an EDI line canonical() sets the quantity in units through units(), so Pinecrest's cap on the quantity as ordered rejects every case line over 150 units 1/1 1 0
load_flags() returns None for empty config, breaking the membership check in gate.py 1/1 1 0
position_of() not-found sentinel changed None -> -1, breaking router's `is None` guard 1/1 1 0
transform() returning nothing now drops the event, and an unchanged handler's transform still returns nothing, dropping every dispute 1/1 1 0
transform() returning nothing now drops the event, and an unchanged handler's transform still returns nothing, dropping every dispute 1/1 1 0
transform() returning nothing now drops the event, and the dispute handler's transform returns noteMissing(), which returns nothing, dropping every dispute 1/1 2 0
transform() returning nothing now drops the event, and the dispute handler's transform returns noteMissing(), which returns nothing, dropping every dispute 1/1 1 0
validate() now skips on a falsy return, and an unchanged handler's validate still returns None, dropping every refund 1/1 1 0
validate() now skips on a falsy return, and an unchanged handler's validate still returns None, dropping every refund 1/1 1 0
validate() now skips on a falsy return, and the refund handler's validate returns note_missing(), which returns the optional fields it found missing: an empty list for every refund that has a reason 1/1 1 0
validate() now skips on a falsy return, and the refund handler's validate returns note_missing(), which returns the optional fields it found missing: an empty list for every refund that has a reason 1/1 1 0

Cal.com · Tier 2 · found 27/36 · 11 cases

CaseFoundFindingsFalse-alarms
Add guest management functionality to existing bookings 4/5 9 0
Advanced date override handling and timezone compatibility improvements 3/4 4 0
Async import of the appStore packages 1/1 2 0
Comprehensive workflow reminder management for booking lifecycle events 1/3 4 0
OAuth credential sync and app integration enhancements 6/7 8 0
SMS workflow reminder retry count tracking 2/3 3 0
feat: 2fa backup codes 2/3 7 0
feat: `Troubleshooter` atom 1/1 4 0
feat: add calendar cache status and actions (#22532) 0/1 7 0
fix: handle collective multiple host on destinationCalendar 6/7 13 0
fix: instant booking location lookup 1/1 3 0

CockroachDB · Tier 2 · found 9/11 · 5 cases

CaseFoundFindingsFalse-alarms
Backup manifest EndKey stored without Clone is corrupted by a caller's scratch-buffer reuse 2/3 6 0
Crud writer feeds tombstone updates a row without stored computed columns, panicking the Deleter 0/1 3 0
Per-statement fnv.New128() allocation is a hot-path throughput regression 4/4 6 0
Tombstone updater re-leases its descriptor on every call and reports failed updates as success 2/2 5 0
Treating min_checkpoint_frequency=0 as 'disabled' stalls the changefeed highwater 1/1 4 0

ComfyUI · Tier 2 · found 0/1 · 1 cases

CaseFoundFindingsFalse-alarms
Add LoRA trainer nodes and image-set loaders 0/1 11 0

Deno · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
fix(npm): handle deno run/install of npm package with only directories.bin 1/1 5 0

Discourse · Tier 2 · found 21/23 · 7 cases

CaseFoundFindingsFalse-alarms
Add comprehensive email validation for blocked users 1/1 3 0
Enhance embed URL handling and validation system 5/5 11 0
FEATURE: Can edit category/host relationships for embedding 8/8 8 0
FEATURE: automatically downsize large images 3/4 6 0
FEATURE: per-topic unsubscribe option in emails 2/2 2 0
FIX: proper handling of group memberships 1/2 9 0
Optimize header layout performance with flexbox mixins 1/1 2 0

Django · Tier 2 · found 2/2 · 1 cases

CaseFoundFindingsFalse-alarms
Fixed #36273 -- Moved Index system checks from Model to Index.check(). 2/2 4 0

Formbricks · Tier 2 · found 3/4 · 2 cases

CaseFoundFindingsFalse-alarms
Add response-pipeline webhook delivery job 1/1 3 0
Storage auth session path uses a role-blind access check, letting billing-role users escalate 2/3 2 0

Grafana · Tier 2 · found 18/19 · 9 cases

CaseFoundFindingsFalse-alarms
Advanced SQL Analytics Framework 2/2 2 0
Anonymous: Add configurable device limit 2/2 5 0
AuthZService: improve authz caching 1/2 2 0
DashboardDS: Fix Mixed panels not updating on time-range change with stale upstreams 1/1 1 0
Database Performance Optimizations 2/2 3 0
Dual Storage Architecture 4/4 7 0
Frontend Asset Optimization 1/1 1 0
Notification Rule Processing Engine 3/3 9 0
Unified Storage Performance Optimizations 2/2 3 0

Keycloak · Tier 2 · found 12/14 · 9 cases

CaseFoundFindingsFalse-alarms
Add AuthzClientCryptoProvider for authorization client cryptographic operations 2/2 6 0
Add Client resource type and scopes to authorization schema 1/1 6 0
Add Groups resource type and scopes to authorization schema 3/3 3 0
Add HTML sanitizer for translated message resources 0/1 4 0
Add caching support for IdentityProviderStorageProvider.getForLogin operations 1/1 2 0
Add rolling-updates feature flag and compatibility framework trap 1 0
Fix concurrent group access to prevent NullPointerException 1/1 3 0
Fixing Re-authentication with passkeys 1/2 1 0
Implement access token context encoding framework 3/3 5 0

Kubernetes · Tier 2 · found 2/8 · 4 cases

CaseFoundFindingsFalse-alarms
Reduce cache locking duration when the DaemonSet controller fetches pods 0/1 1 0
Serve LISTs with exact ResourceVersion and continuations from the cache 2/3 3 0
Trim managedFields in the controller-manager and scheduler informer transforms 0/1 1 0
kubelet DRA: update claimInfo cache locking and checkpoint semantics 0/3 6 1

LVGL · Tier 2 · found 3/3 · 1 cases

CaseFoundFindingsFalse-alarms
xml: sync the widget schemas with the runtime parsers 3/3 9 0

mpv · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
player: detect forced subtitle tracks from the filename 1/1 3 0

n8n · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
fix(editor): Load credentials when opening node credential picker 1/1 4 0

NetBeans · Tier 2 · found 1/2 · 2 cases

CaseFoundFindingsFalse-alarms
Extract the source file name from the .class and use it to locate the source 1/1 7 0
LSP: do not compute text edits in source actions on resolve 0/1 3 0

Next.js · Tier 2 · found 9/15 · 4 cases

CaseFoundFindingsFalse-alarms
Image optimizer hardcodes max-age=0, discarding the upstream cache TTL 4/4 11 1
Passing nextConfig: undefined also disables basePath stripping, corrupting router.query 1/1 2 0
Server Action external redirect is dropped when invoked outside a React scope 0/1 3 1
Wrapping the data response in a Buffer misclassifies it as dynamic, dropping Content-Length and ETag 4/9 11 0

Novu · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
Environment scoping added to create/update integration routes but not the sibling mutations 1/1 3 0

OpenCV · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
videoio: add IStreamReader support to the Java bindings 1/1 5 0

PostHog · Tier 2 · found 1/4 · 6 cases

CaseFoundFindingsFalse-alarms
Email-queue routing parks workflow waits on a queue the subscription matcher never searches 1/1 5 0
Hardcoded queue_name='hogflow' filter never finds email-routed parked waits trap 5 0
Narrowing a shared visibility flag hides sync-method/field/primary-key columns for non-SQL sources 0/1 2 0
Raw query uses the HogQL table alias 'logs' instead of the physical 'logs_distributed' 0/1 3 0
Timezone-unpinned toStartOfDay vs UTC-pinned date constants empties keyset page 2 trap 4 1
feat(sig): custom agents 0/1 4 0

Redis Client · Tier 2 · found 1/2 · 1 cases

CaseFoundFindingsFalse-alarms
Implement Write Barriers for HiredisConnection 1/2 1 0

Sentry · Tier 2 · found 20/23 · 10 cases

CaseFoundFindingsFalse-alarms
Enhanced Pagination Performance for High-Volume Audit Logs 4/4 4 0
GitHub OAuth Security Enhancement 2/2 4 0
GitLab integration search returns full project paths 2/2 5 0
Optimize spans buffer insertion with eviction during insert 3/3 9 0
Span Buffer Multiprocess Enhancement with Health Monitoring 1/2 5 0
Span tree minimap and secondary panel 1/2 5 0
feat(ecosystem): Implement cross-system issue synchronization 1/1 1 0
feat(upsampling) - Support upsampled error count with performance optimizations 3/4 6 0
feat(uptime): Add ability to use queues to manage parallelism 2/2 5 0
feat(workflow_engine): Add in hook for producing occurrences from the stateful detector 1/1 2 0

SigNoz · Tier 2 · found 5/11 · 2 cases

CaseFoundFindingsFalse-alarms
chore: recognize variable in expression 4/9 10 0
fix: do not sort in descending locally if the other is explicitly specified 1/2 3 0

TaskFlow (Convex) · Tier 2 · found 11/13 · 10 cases

CaseFoundFindingsFalse-alarms
.collect() Just to Count (TaskFlow PR #6) 1/1 1 0
.filter() vs Index (TaskFlow PR #2) 1/1 1 0
Authorization Bypass (TaskFlow PR #10) 2/2 4 0
Exposed Internals (TaskFlow PR #4) 1/1 2 0
Missing Aggregate Update (TaskFlow PR #8) 1/1 2 0
Missing Auth Check (TaskFlow PR #3) 1/1 3 0
Nested Lookups (TaskFlow PR #1) trap 0 0
OCC Conflict on Hot Path (TaskFlow PR #9) 1/1 3 0
Unbounded .collect() (TaskFlow PR #5) 1/1 1 0
Unbounded Array in Document (TaskFlow PR #7) 2/4 3 0

Tauri · Tier 2 · found 1/1 · 1 cases

CaseFoundFindingsFalse-alarms
fix(core): Correctly detect Android Tauri configuration file, closes #7785 1/1 5 0