crbench//

Claude Code (Opus 5.5)

Latest run 2026-10-25-s1 · model cli-claude-opus-5-5

53%
Rating · High
95% 47%–59% · 1016 matchups
79.3%
Coverage
77.6%
Cross-File
30/37
Security
77% severity-weighted
92.6%
Validity
7.2%
False-alarms
127
Cases (100%)

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

vs Cubicvs 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 3/5 (60.0%)
The diff replaces the TOTP branch with `if (user.twoFactorEnabled && credentials.backupCode)`, which takes priority over TOTP verification, while the unchanged password gate above it verifies the password only when `totpCode` is falsy (`if (user.password && !credentials.totpCode)`). Posting an email, any non-empty `totpCode`, and a stolen backup code therefore skips the password check and authenticates on the backup code alone, without the password and without ever reaching TOTP verification.
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 88/108 (81.5%)
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 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.
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.
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.
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 standalone-without-sharp guard inside imageOptimizer's Squoosh-fallback branch, the deliberate `throw new ImageError(500, 'internal server error')` (meant to hard-fail when 'sharp' isn't installed in standalone mode) is caught by the enclosing try/catch, which returns { buffer: upstreamBuffer, contentType: upstreamType!, maxAge } instead of propagating the error. The old code sent a real 500 directly (`req.statusCode = 500; res.end(...); return { finished: true }`); this diff's rewrite routes the same guardrail through a throw that gets silently swallowed, so standalone mode without sharp serves a 200 with the original, unoptimized image instead of failing loudly.
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.
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).
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.
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.
The rewritten `reload()` reads the current target out of the config handle with `if let Some(conf) = &*config_handle().lock().unwrap()` and calls `get_internal` from inside that block. The `MutexGuard` is a temporary in the `if let` scrutinee, so it is alive for the whole body rather than being dropped at the end of the statement, and `get_internal` locks the same `Mutex` again when it stores the freshly parsed config (`*config_handle().lock().unwrap() = Some(ConfigMetadata { .. })`). `std::sync::Mutex` is not re-entrant, so the second lock blocks on a guard held by the same thread and the process hangs with no error and no panic. The caller is the dev-server file watcher (`tooling/cli/src/dev.rs` calls `reload_config` when tauri.conf.json changes), so `tauri dev` deadlocks on the first config edit — the exact workflow the PR set out to improve.
medium 71/91 (78.0%)
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.
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 interface gains `createEvent(event, credentialId)` and Google selects its calendar by matching that credential, but the Office365 (and Lark) implementation still destructures `const [mainHostDestinationCalendar] = event.destinationCalendar ?? []` and builds the request path from element zero, ignoring the credential. `EventManager.createAllCalendarEvents` now loops once per host credential, so every iteration writes to the organizer's calendar id under a different member's token.
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.
`sendAddGuestsEmails` takes no event-type metadata and unconditionally sends to the organizer, every team member and every attendee, while every other booking-lifecycle sender in the same file gates on the helpers that read `disableStandardEmails.all.host` and `.attendee`. The handler already loads the event type, so the metadata is in hand and simply not passed, and an organizer who disabled standard emails still has them sent.
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.)
`resetAndMaybeDumpStats` copies and re-makes `a.stmts` but the diff's new per-fingerprint `a.txns` map is neither transferred to the copy nor cleared. Transaction statistics therefore survive every reset, are never handed to the reported-stats sink, and accumulate one entry per distinct transaction fingerprint for the lifetime of the node.
`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.
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.
In getClientsWithPermission(String scope), iterating resourceStore.findByType(server, AdminPermissionsSchema.CLIENTS_RESOURCE_TYPE) and returning resource.getName() will only ever consider the type-level 'Clients' resource (per-client resources have no type) and return its name, while AvailableRoleMappingResource#getRoleIdsWithPermissions expects actual client IDs to pass to realm.getClientById, which can lead to incorrect behavior or a null client and subsequent failures.
The client-credentials grant builds its token through `tokenManager.responseBuilder(...).generateAccessToken()` directly, bypassing the shared response path where the diff sets `Constants.GRANT_TYPE` on the client session context. `initToken` then reads that attribute, finds it null and substitutes the unknown marker, so every client-credentials token id encodes `na` rather than the shortcut the diff registers for this grant. Every other direct-responseBuilder path in the PR was updated; this one was missed.
The textarea XML schema is changed to declare the placeholder property as `placeholder_text`, but the textarea XML parser, which the change does not touch, still matches only the attribute name `placeholder`. XML written against the updated schema, such as `<lv_textarea placeholder_text="Type here"/>`, matches no branch in the parser's attribute chain, so `lv_textarea_set_placeholder_text` is never called. The attribute loop has no unknown-attribute warning, so the placeholder is dropped silently.
The new tabview tab-button create callback reads the optional `index` attribute and passes the result straight to the XML integer parser. A missing attribute makes the lookup return NULL and the parser dereferences it immediately, so any XML using the tab-button element without an explicit index crashes once the tabview already has a tab, instead of falling back to the first tab.
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.
OAuth state uses pipeline.signature (static) instead of a per-request random value
The upsampling eligibility check passes the outer dataset instead of the actual dataset used by scoped_dataset. In paths where the query ultimately runs against discover (e.g., dashboard split) while the original dataset is metrics, upsampling may be skipped even when all projects are allowlisted.
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.
The new `HasOrderSpecified()` type-switches over the trace, log, metric and formula query types and omits `QueryBuilderTraceOperator`, which carries its own `Order` field and is a first-class member of the same pipeline. `applyDefaultSort` is therefore true for a trace-operator query that did specify an order, and the scalar formatter re-sorts by the first aggregation -- the descending re-sort this PR exists to suppress.
low 26/32 (81.2%)
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.
Wrapping `.small-action` in `@include flexbox()` (topic-post.scss) silently breaks the layout of its children. `.small-action` still contains the pre-existing `button { float: right }`, `.topic-avatar { float: left }`, and `clear: both`, but floats are ignored on flex items, so the action button is no longer right-aligned and the avatar/desc layout collapses. This is the flexbox side-effect that forced the upstream revert.
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.
The rendered GrafanaRuleListItem is missing the required key prop for React list items. This can cause rendering issues when the list order changes.
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 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.

By diff size — compare every bot

Keeps pace with the field

The gap moves +4 pts from small to large, so it drops off about as much as the other bots do as PRs grow.

Diff sizeCasesBugs caughtCoverageOther bots, same PRsvs othersFalse-alarms
small ≤100 lines 54 59/64 93% 86% +7 pts 5%
medium 101–500 lines 40 60/74 78% 72% +5 pts 10%
large >500 lines 33 69/98 70% 59% +11 pts 6%

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 0.4 min and 90th percentile 0.9 min over 127 reviews.

Diff sizeReviewsMedian90th percentile
small ≤100 lines540.2 min0.6 min
medium 101–500 lines400.5 min1.0 min
large >500 lines330.6 min1.0 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-10-10-s178.3%92.6%119
2026-10-25-s1100.0%92.3%8

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 3 0
Binary-sink migration missed an unchanged Serializer implementer (CsvSerializer still returns str) 1/1 2 0
Binding the tenant scope with `let _ =` drops the guard at once, so the digest reads every tenant's rows 1/1 2 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 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 2 0
Lowercasing tags silently breaks the case-sensitive admin check in access.py 1/1 2 0
Moving the Server Action redirect into the render commit drops it on the unchanged non-React result path 1/2 2 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 2 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 2 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 2 0
The cached shipment payload changes shape without bumping CACHE_VERSION, so old entries are read as current 1/1 2 0
The cached shipment payload changes shape without bumping CACHE_VERSION, so old entries are read as current 1/1 2 0
The location record gains a field but the TypeScript client decoder keeps the old record layout 1/1 3 1
The location record gains a field but the TypeScript client decoder keeps the old record layout 1/1 3 1
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 2 1
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 2 0
transform() returning nothing now drops the event, and an unchanged handler's transform still returns nothing, dropping every dispute 1/1 2 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 2 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 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 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 1/1 1 0

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

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

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

CaseFoundFindingsFalse-alarms
Backup manifest EndKey stored without Clone is corrupted by a caller's scratch-buffer reuse 2/3 4 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 2/4 4 0
Tombstone updater re-leases its descriptor on every call and reports failed updates as success 2/2 3 1
Treating min_checkpoint_frequency=0 as 'disabled' stalls the changefeed highwater 1/1 3 0

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

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

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 4 0

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

CaseFoundFindingsFalse-alarms
Add comprehensive email validation for blocked users 1/1 4 1
Enhance embed URL handling and validation system 4/5 11 1
FEATURE: Can edit category/host relationships for embedding 8/8 8 1
FEATURE: automatically downsize large images 4/4 6 0
FEATURE: per-topic unsubscribe option in emails 2/2 5 1
FIX: proper handling of group memberships 2/2 6 0
Optimize header layout performance with flexbox mixins 0/1 3 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 5 1
Storage auth session path uses a role-blind access check, letting billing-role users escalate 2/3 3 1

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

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

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

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

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

CaseFoundFindingsFalse-alarms
Reduce cache locking duration when the DaemonSet controller fetches pods 0/1 3 1
Serve LISTs with exact ResourceVersion and continuations from the cache 0/3 0 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 3 0

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

CaseFoundFindingsFalse-alarms
xml: sync the widget schemas with the runtime parsers 1/3 8 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 3 0

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

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

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

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

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 0 0

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

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

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

CaseFoundFindingsFalse-alarms
Email-queue routing parks workflow waits on a queue the subscription matcher never searches 1/1 3 0
Hardcoded queue_name='hogflow' filter never finds email-routed parked waits trap 5 1
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 1/1 3 0

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

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

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

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

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

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

TaskFlow (Convex) · Tier 2 · found 12/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 3 0
Exposed Internals (TaskFlow PR #4) 1/1 3 0
Missing Aggregate Update (TaskFlow PR #8) 1/1 1 0
Missing Auth Check (TaskFlow PR #3) 1/1 3 0
Nested Lookups (TaskFlow PR #1) trap 1 1
OCC Conflict on Hot Path (TaskFlow PR #9) 1/1 4 0
Unbounded .collect() (TaskFlow PR #5) 1/1 2 0
Unbounded Array in Document (TaskFlow PR #7) 3/4 3 0

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

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