crbench//

Cubic

Latest run 2026-10-25 · website ↗

38%
Rating · High
95% 32%–44% · 1016 matchups
62.4%
Coverage
52.9%
Cross-File
24/37
Security
68% severity-weighted
90.6%
Validity
8.3%
False-alarms
127
Cases (100%)

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

vs Claude Code (Opus 5.5)vs cursorvs Drape (Deep Review)vs Drape (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 67/108 (62.0%)
The diff makes normalize_tags() lowercase tags — a plausible normalization. But the unchanged consumer access.is_admin() compares against the capitalized literal "Admin", so after lowercasing the membership test never matches and every admin silently loses admin status. No exception is raised; the change looks like a clean improvement in isolation and the break is only visible through the unchanged consumer access.py.
EventManager.ts:170 now writes credentialId: undefined for video booking references (was result.credentialId from videoClient.ts:78), so handleCancelBooking.ts:491's `if (bookingVideoReference.credentialId)` guard is always false and the external video meeting is never deleted on cancellation.
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.
TopicRetriever fetches the embed/feed URL with `open(url).read` (Readability) and `open(SiteSetting.feed_polling_url)`. The only guard is `invalid_host?`, which pins the initial referer/embeddable_host; open-uri transparently follows HTTP redirects, so a whitelisted host returning a 3xx to an internal address (link-local 169.254.169.254, a private IP, or a localhost admin port) reaches it. This is a redirect-based SSRF that the host whitelist does not cover.
The TopicEmbed.import method is susceptible to a NoMethodError if the contents parameter is nil when attempting to append a string, and an XSS vulnerability due to unescaped url interpolation in the generated HTML.
Because flusher processes are created via multiprocessing.get_context('spawn').Process, they are instances of multiprocessing.context.SpawnProcess, which on POSIX is not a subclass of multiprocessing.Process, so this isinstance check will always be false and hung processes won't be killed here.
SimpleQueueProcessingStrategy.close()/join()/terminate() (queue_consumer.py:335-342) call queue_pool.shutdown() on the factory-shared FixedQueuePool during arroyo's partition-revocation rebalance, so the next create_with_partitions reuses the now-shut-down pool whose work_queue.put() raises queue.ShutDown — swallowed by submit()'s broad except, which then marks offsets complete, silently dropping all messages and committing their offsets after the first rebalance.
When requests are authenticated with API keys or org auth tokens (which have user_id=None), organization_context.member is None. Line 71 attempts to access organization_context.member.has_global_access without checking if member is None, causing an AttributeError crash when optimized_pagination=true is used, even though the request passed all permission checks with valid org:write scope.
RouteCard() is changed to send Amex to the Adyen gateway instead of Stripe — a plausible routing tweak with no local smell. But the unchanged consumer capabilities.go records that this service's Adyen integration only handles Visa and Mastercard, so Amex payments routed there can no longer be processed. Whether the legacy gateway supports Amex is a codebase-specific fact stated only in the unchanged Supports(); a diff-only reviewer has no basis to know the reroute is wrong.
The change narrows shouldShowSyncColumns() with `&& conn.supportsColumnSelection`, which is correct for the column-selection control. But the unchanged consumer wizard.ts uses that same gate to show the sync-method and primary-key controls too. For any connector that does not support column selection, those two controls now silently disappear, so the user can no longer choose incremental vs full-refresh sync. The fix is a separate gate for column selection.
The change adds the assertSameEnv() environment-scoping guard to the create() and update() mutations, but the sibling remove() on the same controller is left unguarded. An API key scoped to one environment can therefore delete an integration in another environment of the same org (a cross-environment IDOR). The vulnerable line is the unchanged remove(): the diff shows the guard being added to its siblings, not to it.
sameElidedPrefix(newSpan.Key, lastFile.Span.EndKey, ...) is structurally always true in the contiguous-extend path, since isContiguousSpan requires newSpan.Key == lastFile.Span.EndKey by definition -- comparing ElidedPrefix(X) to itself. The guard therefore cannot fire on the exact path it exists to protect: extending a manifest file across a contiguous span whose elided prefix differs from s.elidedPrefix silently mislabels the entry's key-strip prefix, corrupting restore for ordinary backup shapes (a table's span ending where the next table's begins). Distinct from d1 -- same function, different mechanism. The sibling file_sst_sink.go compares spanPrefix against s.elidedPrefix directly and does not have this bug.
getDeleter re-acquires when `!timestamp.After(expiration)` (timestamp <= expiration), which is the lease's valid range, so it re-leases every call while valid and reuses the expired descriptor (setting a past UpdateDeadline) once timestamp > expiration — inverted relative to hasExpired's `expiration.LessEq(timestamp)`.
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.
Passing `nextConfig: __NEXT_HAS_REWRITES ? undefined : nextConfig` to getNextPathnameInfo was meant to preserve the locale prefix, but disabling the whole config also disables basePath stripping. The `/_next/data/<buildId>/...` prefix is never removed, and on a catch-all route the route regex overwrites router.query.<param> with the leftover data-URL segments, producing malformed URLs and 404s when basePath + rewrites + middleware + dynamic routes combine.
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.)
In app-page.ts the resume-render branch calls getFallbackRouteParams(pathname) where pathname (parsedUrl.pathname, interpolated in prepare()) is the resolved concrete path with no [param] segments, so getRouteRegex finds no dynamic keys and returns null; it should use normalizedSrcPage (the route pattern) as the sibling PPR-fallback call and the original base-server pathname (match.definition.pathname) did, breaking PPR fallback-shell param postponement for dynamic routes when renderFallbackShell is set in production.
In the app-route template's on-demand-revalidate path, responseGenerator correctly writes a real 404 response (res.statusCode = 404; res.end(...)) and returns null when isOnDemandRevalidate && revalidateOnlyGenerated && !previousCacheEntry. Back in handleResponse, because this route is ISR-eligible (isIsr is true -- it's determined solely by prerender-manifest membership, independent of the on-demand-revalidate flags, and on-demand revalidation is inherently an ISR-only feature), the `if (!isIsr) return null` short-circuit is skipped, and cacheEntry?.value?.kind !== CachedRouteKind.APP_ROUTE (true, since cacheEntry is null) throws an "Invariant: app-route received invalid cache entry" error -- even though a valid 404 HTTP response was already sent to the client. Because isIsr is true, the surrounding catch re-throws this spurious error rather than swallowing it, propagating it up through base-server onto an already-ended response.
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.
The PR added API-key environment scoping to only the create and update integration routes. The sibling mutations removeIntegration, setIntegrationAsPrimary, and autoConfigureIntegration on the same controller were left unscoped, so an API key from one environment can delete, re-prioritize, or auto-configure integrations in another environment of the same org (cross-environment IDOR).
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 listWithTeamHandler (packages/trpc/server/routers/viewer/eventTypes/listWithTeam.handler.ts), this PR adds `AND "public"."EventType"."teamId" IS NULL` to the WHERE clause of Part 1 of the raw SQL UNION query. Part 1 previously returned every EventType owned by the current user (`userId = currentUser`); the new condition restricts it to non-team event types only. Team event types are then expected to come from Part 2, which discovers them via an INNER JOIN on Membership. But a team event type whose `userId` is set to the current user while that user has no Membership row for the team falls through both branches: Part 1 excludes it (teamId is not null) and Part 2 excludes it (no Membership). The result is that such owned team event types silently disappear from the listing, breaking the event-types view for owners-without-membership.
In useBookings, this PR renames the instant-booking query parameter from bookingId (a number) to bookingUid (a string), but the getInstantBookingLocation query is still gated only on `enabled: !!bookingUid` with no isInstantMeeting guard. A non-instant "additional seats" booking flow carries a bookingUid in the URL (Booker store setSeatedEventData), so the query now fires for it; when the existing booking's metadata has a videoCallUrl, RedirectToInstantMeetingModal pushes the booker to that video page, and otherwise an error toast shows. Either way the seat cannot be booked. Before the rename the value was read as `parseInt(getQueryParam("bookingId") ?? "0")`, which was 0 (falsy, query disabled) on those URLs, so the rename is what newly triggers the path. The fix gates both the query and the redirect effect on isInstantMeeting.
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.
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`.
Limited consistent LISTs bypass the watch cache and hit etcd. For a consistent read the delegator sets `opts.ResourceVersion` to the current etcd RV, so in `watchCache.list` the new "legacy exact match" branch (`Limit > 0 && len(opts.ResourceVersion) > 0 && opts.ResourceVersion != "0"`) now matches and routes the request to `listExactRV`. With `ListFromCacheSnapshot` off (its default) the snapshot store is nil, so `listExactRV` returns `ResourceExpired` and the delegator falls back to etcd. The net effect is that in the default config every consistent LIST that carries a limit (e.g. `GET /pods?limit=500`) now bypasses the cache and queries etcd directly; even with snapshots enabled it drops the index-based prefiltering that `listLatestRV` would apply.
Continue requests are served from a cache snapshot without a freshness wait, so a lagging cache returns a stale, incomplete page. A continue request carries no explicit ResourceVersion (forbidden), so `Cacher.GetList` computes `listRV = 0` and `WaitUntilFreshAndList` does not block; the serve path then calls `listExactRV(key, continueKey, continueRV)` -> `snapshots.GetLessOrEqual(continueRV)`, which returns the greatest snapshot <= continueRV even when the cache has not reached continueRV, and labels the response `ResourceVersion = continueRV`. In an HA cluster a continue token minted by a fresh apiserver A and routed to an apiserver B whose watch cache lags continueRV yields an older snapshot's page mislabeled at continueRV, silently dropping objects created in (snapshotRV, continueRV].
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.
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.
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.
In pkg/querybuilder/where_clause_visitor.go the new variable-recognition blocks in VisitComparison slice var_ with var_[1:] (to retry the variable lookup without a leading '$') guarded only by a string type assertion: "if var_, ok := value.(string); ok" / "if var_, ok := values[0].(string); ok". An empty string passes that assertion, and var_[1:] on "" panics with "slice bounds out of range [1:0]", crashing the request goroutine / query service. It is reachable: a filter expression value of '' (empty quoted literal) flows through VisitValue -> trimQuotes("''") -> "" into both the single-value comparison path and the IN/NOT IN path.
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.
hiredis_read_internal stores the address of its stack-local reader_state in connection->context->reader->privdata. Ruby's YJIT can move execution to a different native stack while hiredis retains that pointer, so reply_append later dereferences invalid stack memory. Parsing a Redis response can then read a corrupt task_index pointer and crash the process with SIGSEGV.
The diff gives check the canonical values the checks compare: Channel.run() (portside/channels/base.py) now calls check with `{**record, **self.canonical(record)}` and passes prepare the partner's record as before. Each family base already had a canonical(), which run() logs with every reject: it reads the SKU, quantity, currency and (for storefronts) email from the partner's fields, normalised the way prepare does, through readable() (portside/channels/fields.py), and each family's check ends by reading them strictly, so a channel's own check only runs on a line whose canonical values can be read. The diff changes no hook's signature or return contract and no family base, and the seven channel checks that read one of those fields under another name or normalised it themselves read the canonical value instead. For an EDI line, EdiChannel.canonical() (portside/channels/edi/base.py), which the diff doesn't touch, sets `"quantity": units(record["quantity"], record["uom"], record.get("pack"))`, the canonical quantity prepare also writes through line_totals() (fields.py): the PO line's quantity as ordered (in cases for a CS line) times the pack size. PinecrestChannel.check (portside/channels/edi/pinecrest.py), which the diff doesn't touch, rejects a line when `parse_quantity(record["quantity"]) > self.MAX_QUANTITY` (150), a cap on what one PO line orders that catches a UPC sent in the quantity field. It now compares units against that cap, so every Pinecrest case line over 150 units (13 cases of 12, 26 cases of 6) is rejected as "more than 150 ordered", and those purchase orders are dropped from the warehouse as partner errors. Nothing in the class is wrong on its own and the repo's Pinecrest test (6 cases of 12) passes either way. The other canonical values hold for every check that reads them: a marketplace quantity (Tessera's cap) is only parsed to an int, the register amounts aren't canonicalised, and the SKU, currency and email checks see the same normalisation prepare applies, which changes their outcome only for the partner formats the PR is for.
The diff gives check the canonical values the checks compare: Channel.run() (portside/channels/base.py) now calls check with `{**record, **self.canonical(record)}` and passes prepare the partner's record as before. Each family base already had a canonical(), which run() logs with every reject: it reads the SKU, quantity, currency and (for storefronts) email from the partner's fields, normalised the way prepare does, through readable() (portside/channels/fields.py), and each family's check ends by reading them strictly, so a channel's own check only runs on a line whose canonical values can be read. The diff changes no hook's signature or return contract and no family base, and the seven channel checks that read one of those fields under another name or normalised it themselves read the canonical value instead. For an EDI line, EdiChannel.canonical() (portside/channels/edi/base.py), which the diff doesn't touch, sets `"quantity": units(record["quantity"], record["uom"], record.get("pack"))`, the canonical quantity prepare also writes through line_totals() (fields.py): the PO line's quantity as ordered (in cases for a CS line) times the pack size. PinecrestChannel.check (portside/channels/edi/pinecrest.py), which the diff doesn't touch, rejects a line when `parse_quantity(record["quantity"]) > self.MAX_QUANTITY` (150), a cap on what one PO line orders that catches a UPC sent in the quantity field. It now compares units against that cap, so every Pinecrest case line over 150 units (13 cases of 12, 26 cases of 6) is rejected as "more than 150 ordered", and those purchase orders are dropped from the warehouse as partner errors. Nothing in the class is wrong on its own and the repo's Pinecrest test (6 cases of 12) passes either way. The other canonical values hold for every check that reads them: a marketplace quantity (Tessera's cap) is only parsed to an int, the register amounts aren't canonicalised, and the SKU, currency and email checks see the same normalisation prepare applies, which changes their outcome only for the partner formats the PR is for. The project's history shows the habit the diff breaks: each earlier change to how run() calls the stages (stripping text fields before them, running them from the `stages` list, keeping one channel instance per process) changed, in the same commit, the channels that depended on the old behaviour (Kestrel's PO-length check for the stripping, Tillwise's per-file state for the shared instance).
The diff changes the contract of Handler.validate (sightline/handlers/base.py): it used to raise RecordRejected to reject a record with its return value ignored, and now returns True to keep a record and False to skip it, with run() doing `if not keep: result.skipped += 1; continue`. It adds `return True` to every handler whose validate fell off the end, and turns the expected-traffic rejects into `return False`. It leaves alone the handlers whose validate already ended with a return: the family bases (`return super().validate(record)`), the 25 handlers that end `return present(record, self.kind, ...)` (sightline/fields.py), which returns True or raises, and RefundHandler (sightline/handlers/billing/refund.py), whose validate ends `return note_missing(record, self.kind, "reason")`. note_missing() logs the optional fields a record lacks and returns their names, so for a refund that has a reason it returns an empty list. That was harmless while validate's return value was ignored; now run() reads the empty list as "skip", and every refund that carries a reason (all of them, in practice) never becomes a row: net revenue on the warehouse side silently stops subtracting refunds, with nothing rejected and no error. A refund without a reason is kept. The other handlers that call note_missing() call it as a statement and now return True after it. The handlers are found through the registry that Handler.__init_subclass__ fills. The money family base's @audited wrapper returns the hook's result for reversals and other records alike, and overrides of validate carry no return annotation, so neither shows the contract either way.
The diff changes how handlers are built and called: ingestEvents (ingest.ts) used to call createHandler, which built a new handler for every event, and now calls handlerFor (registry.ts), which builds one handler per event type and HandlerContext on first use and hands every later event of that type to the same instance; it updates the lifetime in the Handler doc comment and docs/handlers.md. Handler.run() already started every event with an empty postings list and a new copy of the event, and no hook's signature or contract changes. PayoutPaidHandler (payout-paid.handler.ts), which the diff doesn't touch, charges the flat payout fee through `this.ctx.fees.payout(this).charge(line.account, line.currency)`. The fee schedule (FeeSchedule in fees.ts), also untouched, keeps one PayoutFees per owner in a WeakMap, so the PayoutFees payout.paid asks for lives exactly as long as the handler. PayoutFees (payout-fees.ts) remembers the accounts it has charged in a Set and returns the flat fee only the first time it sees an account, which implemented the pricing rule "once per seller in a payout" (FeeTable's payoutFlat in fees.ts, and the payout test) while each payout got a new handler and so a new owner. With one handler for every payout.paid event, a seller is charged on their first payout after the process starts and never again: every later payout posts no payout fee, with no error or reject, and the platform's payout fee revenue and the sellers' balances are off by the fee on every repeat payout. Nothing in the class is wrong on its own, and the repo's payout tests pass (each ingests a single payout). Nothing else a shared handler holds changes behaviour: InstantPayoutHandler asks the fee schedule for the event's PayoutFees (`payout(event, speed)`), so its sellers are charged once per payout either way; the 48 rule handlers' WarnOnce and charge.captured's and transfer.created's LineDedupe hold Sets of keys but clear them when they see a new event object, which run() makes for every event; and the rate cache is the context's, which ingest shared before the change too. The handlers are reached only through the HANDLERS table in registry.ts.
The diff changes what Handler.transform's return value means (handler.ts): it used to be "adjust the default row in place, or return a replacement", with run() posting `this.transform(event, row) ?? row`, and now returning nothing drops the event, with run() doing `if (!row) { result.skipped += 1; continue; }`. It adds `return row` to every handler whose transform adjusted the row in place and returned nothing, and makes charge.succeeded and invoice.paid drop zero amounts. It leaves alone the transforms that already end with a return: the family bases, the 21 payout and fee handlers that end `return withMemo(row, ...)` (annotations.ts), which sets the memo and returns the row, and DisputeCreatedHandler (dispute-created.handler.ts), whose transform calls `super.transform(event, row)` and ends `return noteMissing(event, "reason")`. noteMissing() logs the optional fields the event lacks and returns nothing (`: void`), which TypeScript accepts as a return from a transform typed `LedgerRow | void`. That was harmless while run() fell back to the adjusted row; now run() reads the undefined as "drop", and every charge.dispute.created event is counted as skipped: the amount the provider holds back never reaches the ledger, and the held-funds account and the reconciliation against the provider balance are silently off by every open dispute, with nothing rejected. The other handlers that call noteMissing() call it as a statement and now return the row after it. The HeldFunds mixin's @audited transform returns the hook's result for held funds and other rows alike. The handlers are reached only through registry.ts, which the diff doesn't touch. The project's history shows the habit the diff breaks: each earlier change to a hook's contract in handler.ts (validate throwing InvalidEvent instead of returning a reason, adjust(row, event) renamed transform(event, row)) changed every class and mixin defining that hook in the same commit, and the rename changed audit.ts with them.
With CDP_EMAIL_QUEUE_ROUTING on, a workflow's email step now routes the invocation to the new `email` cyclotron queue, the hog_function action copies that queue onto the flow invocation, and the email worker (a hogflow worker on queue `email`) sends the email and keeps running the flow. A `wait_until_condition` step after it therefore parks the job with queue_name='email', which job-queue-postgres-v2 now persists. The hogflow subscription matcher, unchanged by this diff, wakes parked waits through findParkedJobs, which only looks up `queue_name = 'hogflow'`. It never finds the wait, so a matching event does not advance the workflow and it resumes only on the wait's timeout branch.
medium 53/91 (58.2%)
valid_entries() uses a bare truthiness check (`if e`) but its docstring promises "the non-empty entries." This silently drops legitimate falsy-but-non-empty values too -- 0, 0.0, False, [], {} -- not just "" or None. Any caller passing counts, scores, or booleans loses valid entries with no error raised.
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 adds `await prisma.workflowReminder.update(...)` inside the loop's catch block, which previously held only a `console.log` and so could not fail. Nothing wraps the loop: the handler's only try/catch is the inner one, and the `for` at line 55 closes with no surrounding handler, so a throw from that update escapes the loop and the handler, and `res.status(200).json(...)` is never reached. One reminder's DB failure now aborts the whole batch, where before each iteration was isolated. Reachable: Prisma's update raises P2025 when the row is gone, which this diff makes likelier by adding a deleteMany branch that can remove rows a concurrent cron run is processing. Independent of d2 and d3 -- d2 is the missing `method: SMS` filter on deleteMany, d3 is the locked-account misclassification, and fixing either leaves this failure path in place. Medium rather than high: the unreached reminders keep `scheduled: false` and fall inside the query's `scheduledDate <= now + 7 days` window, so the next cron run picks them up. The loss is fault isolation and a deferred batch, not dropped reminders, and it only reaches a user when a send time falls inside the gap before the next run.
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 cancellation sweep awaits a SendGrid cancel per reminder inside the loop while pushing `prisma.workflowReminder.delete(...)` into an array that is awaited only after the loop. Prisma returns a lazy PrismaPromise that does not execute until awaited, so a SendGrid rejection at index N jumps to the catch and none of the 0..N-1 deletes ever run, while reminders from N onward are never cancelled even though their rows are marked cancelled.
Incorrect end time calculation using slotStartTime instead of slotEndTime
Passing 80% as the dimensions can fail for animated GIFs when allow_animated_thumbnails is true, since the animated path uses gifsicle --resize-fit which expects WxH geometry, not a percentage; downsizing would then silently fail.
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 new plural-ID hydration branch in `_hydrateEmbedded` (added alongside the existing singular path) maps a list of ids through `_lookupSubType` and assigns the result unconditionally: `obj[self.pluralize(subType)] = hydrated || []`. `_lookupSubType` returns `undefined` for an id whose root collection or specific id isn't found; since Array.prototype.map always returns an array, `hydrated` is always truthy and the `|| []` fallback never fires, so the resulting array can contain literal `undefined` entries (e.g. [ModelObj, undefined, ModelObj]). This is the reverse of the existing singular path, which correctly guards with `if (hydrated)` before assigning.
BlockedEmail.should_block? (app/models/blocked_email.rb) increments match_count, sets last_match_at, and calls save; it is invoked from EmailValidator#validate_each, and UsersController#create re-runs validations on both user.valid? (line 168) and user.save (line 172), so a single signup with a matching blocked email writes the row and over-counts match_count twice, plus performs a DB write during the read-only valid? check.
poll_feed.rb calls `i.content.scrub` on every item, but SimpleRSS returns nil for `i.content` on plain RSS 2.0 feeds (body in description/content:encoded absent), so `nil.scrub` raises NoMethodError, aborting the whole un-retried hourly poll and importing nothing.
`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.
The diff removes the fail-fast `IllegalStateException` that rejected multiple crypto providers on the classpath, replacing it with an order-based sort, a debug log and `foundProviders.get(0)`. All three real providers return the same order value, and `Stream.sorted` is stable, so a tie is resolved by ServiceLoader enumeration order: on a deployment carrying both the default and the FIPS provider, which one is selected depends on classpath ordering rather than configuration.
Both group list endpoints drop the hoisted global permission check (`boolean canViewGlobal = groupsEvaluator.canView()`) and filter with a per-group `groupsEvaluator::canView`. Under fine-grained admin permissions v2 that per-group call falls through to a resource lookup and a full uncached policy evaluation, so one evaluation becomes one per group; the subgroup endpoint is worse because it fetches subgroups unbounded and paginates only after filtering.
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
OAuth state uses pipeline.signature (static) instead of a per-request random value
The code attempts to access integration.metadata[sender][login] without checking for the existence of the sender key. This causes a KeyError for integrations where the sender metadata was not set during creation
`OptimizedCursorPaginator.value_from_cursor` returns `cursor.value` raw, an int or float, where `DateTimePaginator` converts it back to an aware datetime. `BasePaginator.build_queryset` splices that value straight into raw SQL, so with `order_by='-datetime'` Postgres is asked to compare a timestamptz against a bigint and raises `operator does not exist`.
The new `upsampled_count` SnQL function in `DiscoverDatasetConfig` (datasets/discover.py) is `toInt64(sum(sample_weight))` with no fallback for a missing weight. Snuba stores `sample_weight` as Nullable(Float64) and writes NULL for any error event that carried no client sample rate, and `sum` skips NULLs. Once events-stats rewrites `count()` to `upsampled_count() as count` for an allowlisted project set, every unweighted event counts as 0 instead of 1, so error charts undercount, and a bucket holding only unweighted events returns NULL instead of its event count.
`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").
Statement IDs are built with `h := fnv.New128()`; the stdlib hash/fnv constructor heap-allocates a hash object on every statement, and the ID is constructed even when not required. On hot SQL paths this is a measurable allocation/throughput regression (the fix's microbenchmarks show kv95 +3.42%). The fix uses a lightweight value-type FNV and only builds the ID when needed. (Large-diff stress case: ~2.8k lines, 14 files.)
The image-optimizer move to response-cache dropped the maxAge argument to sendResponse and hardcoded the cached-image header to `public, max-age=0, must-revalidate` instead of `max-age=${maxAge}`. The computed upstream/minimumCacheTTL maxAge is no longer propagated, so every optimized image returns max-age=0 and CDNs/browsers in front of a single instance stop caching, inflating origin load. (Large-diff stress case: ~3.6k lines, 15 files.)
In imageOptimizer's internal-request path, `if (!mockRes.statusCode)` can never be true for any real HTTP status code (`mockRes.statusCode` starts at 200 and is only ever set to other truthy numbers like 404/500 by `handleRequest`), so the intended check for a failed internal response never fires. The old code additionally forwarded the upstream status via `res.statusCode = mockRes.statusCode`; this diff removes that forwarding entirely, so an internal 404/500 is masked behind an eventual 200 (until a secondary content-type check happens to catch it).
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.
commit() gates the staged navigation on truthiness (`if (state.pendingMpaNavigation)`), so an empty-string url is indistinguishable from the `null` initial state and the redirect is silently skipped. Before the diff the reducer called navigate(action.url) directly with no gate, so navigate("") ran. `Action.url` is typed `string` with no non-empty constraint, so dispatch({ type: "redirect", url: "" }) type-checks at the public boundary. Same falsy-vs-absent collision as t1-py-filter-shifts-pairing d2, introduced here by the new staging step.
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.
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.
`SourceUtils.findMatchingChild` iterates a folder's children and returns the first name match without excluding directories (no `isFolder()` / file-vs-folder check). A directory whose name equals the class name (e.g. a package dir `Test/` next to `Test.java`) is returned as the "source file", so go-to-source resolves to a folder instead of the file. The fix skips folders when matching.
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.
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.
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".
`grid_update` gains an early return when the grid calculation fails, but the calculation has already allocated its row arrays by then and the early return skips the free routine. A grid container that has a row descriptor but no column descriptor, on itself or its parent, gets `c->y` and `c->h` allocated in the row pass and then fails the column pass, leaking both arrays on every layout refresh. Calling the existing free routine at that point is not by itself a safe fix, because the struct is not zeroed on every failure path.
The filename language guesser reuses one `checked_tag` latch for both the hearing-impaired (`sdh`/`hi`/`cc`) and the newly added `forced` suffix, so only the last dot-separated suffix is ever tested as a tag. For a subtitle named `movie.en.sdh.forced.srt` the parser strips `forced`, sets the latch, and then reads `sdh` as the language, returning language "sdh" with the hearing-impaired flag unset. With the suffixes the other way round, `movie.en.forced.sdh.srt`, the six-letter `forced` fails the primary-subtag length check, so no language is found and the forced flag is lost. The wrong language reaches real tracks through subtitle autoload and sub-reload.
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.
low 22/32 (68.8%)
topics#unsubscribe mutates and saves notification_level but is wired to a GET route with check_xhr skipped and no CSRF token, so a cross-site <img>/prefetch or email scanner GET to .../unsubscribe carries the victim's session cookie and silently toggles their topic notification level to muted.
The postMessage origin check uses reversed substring matching (`discourseUrl.indexOf(e.origin) === -1`), accepting any origin that is a substring of the configured Discourse URL rather than requiring an exact origin match; impact is limited to letting a non-Discourse frame resize the embed iframe.
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.
Dead code exists where ASN1Encoder instances are created and written to, but their results are immediately discarded. The actual encoding is performed by new ASN1Encoder instances created in the subsequent return statement, rendering the earlier operations useless.
`_is_error_focused_query` decides eligibility with a bare substring test on the raw query string, with no token boundary and no negation handling, so a query that explicitly excludes errors matches. The events-stats endpoint acts on the result and rewrites `count()` to the upsampled aggregate, so a chart that asked for non-error events is computed from a sample-weight sum those rows do not carry. The damage is realised through d5: with upstream's fallback that counts an unweighted row as one, the misclassified query would still count correctly, so fixing d5 leaves this a latent misclassification.
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 new checklist mutations write no `activityLog` entry, while every other task-mutating operation does: `create`, `update` and `remove` in convex/tasks.ts each call `ctx.runMutation(internal.activity.log, ...)`. A task's checklist can therefore be changed with no record, leaving the activity history incomplete for that class of edit.
`addItem` takes `text: v.string()` and pushes it unchanged, so a blank or whitespace-only item is stored. The only guard is client-side, `if (!newChecklistItem.trim()) return` in TaskDetail.tsx, and a Convex mutation is a public API reachable without that component.
The app-route template's outer catch now calls `routeModule.onRequestError(req, err, {...})` without the fourth `routerServerContext` argument that every other call site in this diff passes. `RouteModule.onRequestError` therefore falls back to a bare `console.error(err)` instead of `routerServerContext.logErrorWithOriginalStack`, so a server started with `quiet: true` now prints route-handler errors, a normal server loses the standard error prefix, and in dev the original-stack logger is skipped.
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.

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 47/64 75% 88% -14 pts 1%
medium 101–500 lines 40 41/74 57% 75% -18 pts 7%
large >500 lines 33 58/98 57% 60% -4 pts 11%

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 3.8 min and 90th percentile 9.5 min over 127 reviews; its first comment came after 3.6 min (median).

Diff sizeReviewsMedian90th percentile
small ≤100 lines542.2 min5.1 min
medium 101–500 lines405.0 min9.5 min
large >500 lines335.3 min10.7 min

Timed from the pull request opening, or the comment that asked for a re-review, to the bot's last comment, so it includes the time the review waited in the vendor's queue. See methodology.

Trajectory — coverage over time

RunCoverageValidityCases
2026-06-1165.5%96.4%57
2026-06-1235.1%92.9%19
2026-06-2171.7%97.6%97
2026-10-0864.0%90.5%118
2026-10-1022.2%100.0%9
2026-10-2537.5%100.0%8

Cases reviewed

Authored · Tier 1 · found 28/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 2 0
A new required TRACKER_GEOCODER_URL setting is not added to the Helm chart, so every pod fails at startup 1/1 2 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 1 0
Environment scoping added to create/update but not the sibling delete leaves a cross-env IDOR 1/2 1 0
Filtering empty entries silently misaligns audit's positional entry/timestamp pairing 1/2 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 0/1 0 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 0/1 0 0
Moving the Server Action redirect into the render commit drops it on the unchanged non-React result path 1/2 1 0
Narrowing a shared visibility gate for one control silently hides two unrelated controls 0/1 0 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 0/1 0 0
Sorting the roster silently misaligns payroll's positional name/amount pairing 1/1 1 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 1 0
Switching flusher workers to the spawn context silently disables the reaper's isinstance-gated kill 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 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 1 0
The location record gains a field but the TypeScript client decoder keeps the old record layout 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 0/1 0 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 0/1 0 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 1 0
transform() returning nothing now drops the event, and the dispute handler's transform returns noteMissing(), which returns nothing, dropping every dispute 0/1 0 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 2 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 0/1 0 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 5/5 11 0
Advanced date override handling and timezone compatibility improvements 2/4 4 0
Async import of the appStore packages 1/1 5 1
Comprehensive workflow reminder management for booking lifecycle events 1/3 4 2
OAuth credential sync and app integration enhancements 7/7 15 0
SMS workflow reminder retry count tracking 2/3 2 0
feat: 2fa backup codes 2/3 10 1
feat: `Troubleshooter` atom 0/1 10 3
feat: add calendar cache status and actions (#22532) 1/1 9 0
fix: handle collective multiple host on destinationCalendar 6/7 15 0
fix: instant booking location lookup 0/1 2 0

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

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

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

CaseFoundFindingsFalse-alarms
Add LoRA trainer nodes and image-set loaders 0/1 10 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 2 0

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

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

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

CaseFoundFindingsFalse-alarms
Fixed #36273 -- Moved Index system checks from Model to Index.check(). 2/2 3 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 5 2

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 2 0
AuthZService: improve authz caching 1/2 2 0
DashboardDS: Fix Mixed panels not updating on time-range change with stale upstreams 1/1 2 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 5 0
Unified Storage Performance Optimizations 2/2 3 0

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

CaseFoundFindingsFalse-alarms
Add AuthzClientCryptoProvider for authorization client cryptographic operations 0/2 8 1
Add Client resource type and scopes to authorization schema 1/1 5 1
Add Groups resource type and scopes to authorization schema 2/3 6 1
Add HTML sanitizer for translated message resources 0/1 8 1
Add caching support for IdentityProviderStorageProvider.getForLogin operations 1/1 1 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 3 0
Implement access token context encoding framework 3/3 7 0

Kubernetes · Tier 2 · found 1/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 0/3 2 0
Trim managedFields in the controller-manager and scheduler informer transforms 0/1 0 0
kubelet DRA: update claimInfo cache locking and checkpoint semantics 1/3 3 1

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

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

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

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

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

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

NetBeans · Tier 2 · found 0/2 · 2 cases

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

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

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

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

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

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

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

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

CaseFoundFindingsFalse-alarms
Email-queue routing parks workflow waits on a queue the subscription matcher never searches 0/1 3 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 3 1
Raw query uses the HogQL table alias 'logs' instead of the physical 'logs_distributed' 0/1 3 1
Timezone-unpinned toStartOfDay vs UTC-pinned date constants empties keyset page 2 trap 1 0
feat(sig): custom agents 0/1 7 0

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

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

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

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

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

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

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

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

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

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