Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
53/100 average clarity
90Strong · 80–100
213Adequate · 60–79
480Thin · 40–59
194Opaque · 0–39
10security candidates with opaque commit messaging
This commit is a simple rename of a code attribute from UseStoreLanguageAttribute to StorefrontRouteAttribute. It only changes the name used in source files and does not alter any program behavior, security settings, or access controls.
This commit changes how the invoice checkout page is translated. Instead of loading translations from separate JSON files in the browser based on a language the customer picks, the page now uses the store's own server-side translation sett…
Removal of client-side language selection reduces attack surface for language-related query-string manipulation (e.g., lang=...)Server-side rendering of checkout strings may reduce exposure to DOM-based XSS via translation files, but no specific vulnerability is shownLarge deletion of locale files and i18next vendor scripts is a cleanup, not a patch
This commit updates two .NET runtime/SDK Docker images to newer patch versions and bumps a third-party library (CsvHelper) from 34.0.0 to 34.1.0. These are routine maintenance updates. The commit message does not say any of the updates fix…
This is a large hardening patch for BTCPay Server that fixes several security weaknesses around account handling, payments, refunds, and plugins. Key changes include: preventing Blazor circuits from staying authenticated after a user's adm…
Blazor circuit principal revalidation against live user stateCookie principal rejection when user is administratively restrictedRefund creation serialized with SELECT FOR UPDATE and single open refund enforcement
20ae3337by Andrew Camilleri (Kukks)+1310−41655 files
This commit removes a per-invoice checkout language option and translates more public-facing text so it can be localized. It is a feature-cleanup and internationalization change, not a security fix. There is no evidence of a vulnerability …
This commit fixes a bug where BTCPay Server's Point of Sale and Crowdfund inventory counts could become wrong after unpaid or expired invoices. Previously, the system could add inventory back multiple times for the same invoice, making it …
Business-logic flaw: inventory counts could be inflated by duplicate restocking eventsState-machine fix: previous status now tracked to prevent double-countingRace/ordering concern mitigated by deterministic event-barrier for tests
This commit fixes a bug in BTCPay Server where marking an already-expired invoice as 'invalid' could cause the app inventory to be restocked twice. The fix tracks each invoice's previous status during status transitions and skips the inven…
Business-logic bug causing duplicate inventory restockingStatus-transition event missing prior-state contextInventory manipulation possible through invoice state changes
This commit adds a new store-level setting that lets merchants choose which language customers see on public pages such as invoices, payment requests, and pull payments. It also marks more text on those pages as translatable. There is no d…
New per-request language scoping via AsyncLocal with explicit BeginRequest/Restore disposalSignalR hub now applies store language to controller calls that bypass MVC filtersRouteStoreResolver centralizes route-value-to-store-id lookup with 10-minute sliding memory-cache
This commit fixes two bugs in BTCPay Server's wallet transaction API. First, when users filtered transactions by both status (confirmed/unconfirmed) and label, the same transaction could appear twice in the results because the filtering lo…
Fixes duplicate entries in API query results due to incorrect filter compositionReplaces unsafe uint256.Parse with uint256.TryParse to prevent unhandled exceptions on malformed inputAdds server-side input validation returning structured 404 API error for invalid transaction IDs
This commit only updates the version tag of the LND (Lightning Network Daemon) Docker image used in test environments from v0.21.7-beta to v0.21.8-beta. It does not change any production application code, configuration logic, or runtime be…
This commit simply bumps the version numbers of three NuGet packages: a test reporting helper and two FIDO2 authentication libraries. There is no indication in the commit itself that these updates fix a security problem, and no external re…
This commit updates many third-party software libraries (NuGet packages) to newer versions and makes small code adjustments so BTCPay Server stays compatible with those updates. The most notable security-relevant change is a rewrite of the…
Dependency version bumps for libraries with known security maintenance value (HtmlSanitizer, Fido2, MailKit, Microsoft.AspNetCore, System.Security.Cryptography.Pkcs)Manual CSV field escaping added to prevent formula/CSV injection in wallet transaction exportsFido2 configuration/AppID handling changed during Fido2 library upgrade
This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when an API key had permissions tied to more than one store. The fix also corrects how usage counts are recorded and displa…
Fixes a UI crash in an administrative API-key usage pageCorrects aggregation of permission usage records when permissions are scoped to specific storesChanges database upsert to persist full permission string including store scope
This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when the same permission (like 'view invoices') was used for more than one store. The fix also corrects how usage counts ar…
Fixes a runtime crash in an administrative API-key usage viewCorrects aggregation of permission usage records that previously could duplicate or conflate store-scoped entriesChanges upsert to persist full permission string including scope, preventing legacy-style policy-only rows from overwriting each other
This commit fixes a math bug in how BTCPay Server rounds very small negative amounts. Previously, a helper called RoundToSignificant divided by the signed value instead of its absolute value, so negative numbers behaved differently from po…
Rounding/truncation bug in financial amount handlingNegative-amount handling asymmetry that could alter displayed or computed balancesFee-bump calculation could fall below Bitcoin incremental relay fee requirement
This commit fixes a crash in the API key authorization page. When a user submits the form without clicking either the 'Authorize' or 'Cancel' button, the server tries to read a missing command value, which could cause an error. The fix saf…
Null dereference in request handling pathUnhandled exception could lead to error disclosure or availability impactDefensive null-safety hardening in controller action
This commit hardens how BTCPay Server downloads translation files from GitHub. It adds checks so the app only fetches files from the project's own trusted GitHub organization, blocks automatic web redirects, and supports a new optional red…
Server-side request forgery (SSRF) protection added: URI host/path validation before outbound fetchAutomatic HTTP redirects disabled for translation update clientManifest redirect field introduced with same-origin/org trust validation
This commit hardens how BTCPay Server downloads translation files from the internet. It adds checks so the server only fetches language packs and manifest redirects from the trusted btcpayserver GitHub organization, turns off automatic HTT…
Server-side request forgery (SSRF) hardening: URI scheme, host, and path prefix are validated before outbound fetchOpen-redirect / HTTP redirect abuse mitigation: AllowAutoRedirect set to false on the translation HttpClientPath traversal mitigation: pack file paths resolved as relative URIs and validated against trusted org prefix
This commit removes old database upgrade scripts (migrations) from before BTCPay Server version 1.12.0 and replaces them with a single consolidated starting schema. It also trims the startup migration task by deleting obsolete data-convers…
Large-scale deletion of database migration historyConsolidation of cumulative schema into a single init SQL scriptRemoval of legacy data-migration logic from startup task
This commit is a large database cleanup: BTCPay Server removed all old EF Core migration files before version 1.12.0 and replaced them with a single consolidated SQL script that creates the current schema from scratch. It also trims the st…
Large schema consolidation could silently drop or alter constraints/indexes compared to the incremental migration historyRemoval of legacy migration executors means installations upgrading from very old versions must rely on the consolidated init script and any remaining IMigrationExecutor implementationsNo explicit security claim or CVE reference in commit message or diff
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedFeature: New global search bar to improve navigation (#7183)by Pavlenex · ea7f7a2f · May 15, 2026 · 46 filesMessage 73 · AdequateInformational 20Details
Commit message · Pavlenex
Feature: New global search bar to improve navigation (#7183)
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 20/100
This commit adds a new global search bar and reorganizes the top navigation in BTCPay Server. Most of the change is user-interface code (menus, CSS, JavaScript, tests). There is one small security-relevant detail: the new search endpoint returns a list of internal URLs and checks whether the current user is authorized for each one, but it also accepts an arbitrary storeId parameter and queries the store with the current user's permissions. The commit does not describe itself as a security fix, and no vulnerability is clearly demonstrated in the diff.
AI review queuedMove code into WalletsPluginby Nicolas Dorier · f2c94dae · May 13, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Move code into WalletsPlugin
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply moves three helper methods that generate wallet-related URLs from a general file into a new file inside the Wallets plugin folder. There is no change to what the code does, no bug fix, and no security-related change.
AI review queuedfix warningsby Nicolas Dorier · 6b676c7b · May 13, 2026 · 2 filesMessage 18 · OpaqueInformational 11Details
Commit message · Nicolas Dorier
fix warnings
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 11/100
This commit removes nullable markers ('?') from some string parameters and adds explicit controller names to two URL helper methods. It is titled 'fix warnings' and appears to be a routine compiler-warning cleanup. There is no direct evidence in the commit that these changes fix a security vulnerability.
Security candidateAllow server admin to specify if an invited user subscribes for monetization or not (#7318)by Chukwuleta Tobechi · 53ba1427 · May 11, 2026 · 15 filesMessage 91 · StrongInformational 21Details
Commit message · Chukwuleta Tobechi
Allow server admin to specify if an invited user subscribes for monetization or not (#7318)
* Option for server-invited users to bypass subscription
* fix code rabbit and include tests
* fix coderabbit test suggestion
* allow for skipping monetization on invite
* code rabbit suggestion
* clean up
* resolve redundant code
* remove view data
* resolve feedback from Nicolas
* restore tests that was removed
91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update path
AI analysis · Informational 21/100
This commit adds a new server-admin-only option called 'Bypass monetization.' When a BTCPay Server instance charges users for subscriptions, admins can now mark specific invited or existing users so they do not need a paid subscription to log in. The change is intentional and exposed through the admin UI; it does not appear to be a hidden backdoor. There is no direct evidence in the commit that it fixes a security bug or introduces a vulnerability, but any feature that lets an admin exempt users from billing controls should be reviewed for authorization and audit-trail completeness.
AI review queuedRemove deprecated Shopify Scripts integration (#6608)by Nicolas Dorier · 0e91f371 · May 8, 2026 · 24 filesMessage 58 · ThinInformational 15Details
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit removes the old Shopify integration from BTCPay Server entirely. It deletes all Shopify-related code, settings pages, API clients, and rate-limiting rules. There is no security patch here—this is a feature removal because Shopify deprecated the underlying technology.
AI review queuedfix: standardize paging in WalletTransactions to use ParseListQuery (#7339)by Abhijay Jain · c6fbe4a8 · May 8, 2026 · 3 filesMessage 85 · StrongInformational 16Details
Commit message · Abhijay Jain
fix: standardize paging in WalletTransactions to use ParseListQuery (#7339)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 16/100
This commit changes how the wallet transactions page reads its paging settings (skip/count). Instead of taking them directly from the URL, it routes them through a shared helper called ParseListQuery that also reads and saves user preferences in a cookie. The change is a code-quality fix to make paging behave consistently with other pages. There is no direct evidence in the commit that this fixes an active security vulnerability, but it removes a place where paging parameters were handled differently from the rest of the application.
Security candidateAdd granular API permissions for on-chain wallets (#7357)by thgO.O · 4a03202a · May 8, 2026 · 5 filesMessage 81 · StrongLow 40Details
Commit message · thgO.O
Add granular API permissions for on-chain wallets (#7357)
* refactor(wallets): align greenfield routes with wallet policies
* fix(wallets): keep payjoin psbt unfinalized before request
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarycredential or privilege statesigning or wallet path
AI analysis · Low 40/100
This commit introduces more fine-grained permission checks for BTCPay Server's on-chain wallet API. Previously, many wallet operations required broad 'modify store settings' or 'view store settings' permissions. Now, operations are gated by dedicated wallet permissions such as viewing wallet data, managing wallet settings, creating/signing/broadcasting transactions, and managing wallet transactions. The change also fixes a Payjoin bug where the PSBT was finalized before the Payjoin request, which could break Payjoin flows. Overall, this is a hardening/security improvement rather than an introduced vulnerability.
AI review queuedMove greenfield wallet controllersby Nicolas Dorier · 74292ad1 · May 7, 2026 · 4 filesMessage 35 · OpaqueInformational 11Details
Commit message · Nicolas Dorier
Move greenfield wallet controllers
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 11/100
This commit simply moves three Greenfield API wallet controller files from one folder to another inside the BTCPay Server codebase and updates their class constructors to use C# primary constructors. The code logic, authorization checks, route URLs, and security behavior appear unchanged. It is a refactoring/organizational change, not a security fix or feature change.
Security candidateMove Wallet ViewModels (#7355)by Nicolas Dorier · 2a9efb52 · May 7, 2026 · 49 filesMessage 43 · ThinInformational 15Details
Commit message · Nicolas Dorier
Move Wallet ViewModels (#7355)
43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Informational 15/100
This commit is a large but straightforward code reorganization: it moves wallet-related view model classes from one namespace/folder (BTCPayServer.Models.WalletViewModels) into a new plugin-specific location (BTCPayServer.Plugins.Wallets.Views.ViewModels) and updates all references accordingly. There is no functional change to how the application behaves, no security fix, and no vulnerability introduced in the diff itself.
Security candidateEnsure the seed isn't leaking to user with can sign permission (#7354)by Nicolas Dorier · dffdda64 · May 7, 2026 · 12 filesMessage 58 · ThinHigh 70Details
Commit message · Nicolas Dorier
Ensure the seed isn't leaking to user with can sign permission (#7354)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege stateseed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · High 70/100
This commit fixes a permission leak in BTCPay Server's hot wallet handling. Previously, users who only had permission to sign transactions ('can sign') could also see the wallet's secret seed phrase, which should be restricted to store administrators. The change introduces a new 'HotwalletSafe' gatekeeper that separates 'can sign' from 'can see seed' and stops the seed from being passed through web forms or displayed to lower-privileged users.
AI review queuedSmall refactorby Nicolas Dorier · 428132cb · May 7, 2026 · 1 fileMessage 18 · OpaqueLow 44Details
Commit message · Nicolas Dorier
Small refactor
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 44/100
This commit refactors authorization checks in two wallet-related controller actions. In one case, the 'clear' command previously required both server-admin role AND store-level wallet-settings permission; now it only requires a server-level policy. In another case, a new switch statement replaces nested if-checks but appears functionally equivalent. The change could be a security fix if the old combined check was overly restrictive, or a security weakening if the new single policy is less protective than the old two-factor check. Without vendor context, the security relevance is uncertain.
AI review queuedMinor refactoringby Nicolas Dorier · ffcc48b7 · May 7, 2026 · 3 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Minor refactoring
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine code cleanup that converts three C# controller classes from traditional constructor syntax to a newer, shorter primary-constructor syntax. It does not change what the code does, what data it accepts, who can access it, or how it protects wallet operations. There is no visible security fix or behavior change.
Security candidateAdd granular wallet permissions and move wallet to plugin (#7329)by thgO.O · 1e1d2514 · May 7, 2026 · 70 filesMessage 58 · ThinLow 45Details
Commit message · thgO.O
Add granular wallet permissions and move wallet to plugin (#7329)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege stateseed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Low 45/100
This is a large refactoring commit that splits BTCPay Server's wallet functionality into a separate plugin and introduces finer-grained wallet permissions (view, create transactions, sign, broadcast, manage settings, etc.). It also adds new tests that verify users with only wallet permissions can access wallet pages and cannot perform actions outside their role. The change is primarily a security-hardening/permission-separation feature, not an obvious vulnerability fix, though it does include one small bug fix for pending-transaction broadcast matching.
Security candidatefeat: add separate CanSendStoreEmail permission for store email API (#7345)by Abhijay Jain · d64288f1 · May 1, 2026 · 3 filesMessage 85 · StrongLow 32Details
Commit message · Abhijay Jain
feat: add separate CanSendStoreEmail permission for store email API (#7345)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege state
AI analysis · Low 32/100
This commit introduces a new, more narrowly-scoped permission called 'CanSendStoreEmail' and applies it to the store email-sending API. Previously, sending store emails required the broader 'CanModifyStoreSettings' permission, which also allows changing many other store settings. This change follows the security principle of least privilege: it lets administrators grant API keys or users the ability to send emails without giving them full power to change store configuration. It is a hardening improvement rather than a fix for an active exploit.
AI review queuedbumpby Nicolas Dorier · a3aaba15 · Apr 24, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
bump
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only changes a single version number in a build file from 2.3.8 to 2.3.9. There is no code change, no bug fix, and no security-related content visible in the diff.
AI review queuedBump 2.3.9by Nicolas Dorier · 33913243 · Apr 24, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Bump 2.3.9
0/100 · OpaqueMessage clarity
! Very short subject! No meaningful explanatory body
This commit only updates the changelog file to add release notes for version 2.3.9. It does not change any source code, configuration, or executable files. There is no security-relevant change in the diff itself.
AI review queuedFix: Server not recovering after a plugin crash (#7335)by Nicolas Dorier · e21e1b73 · Apr 24, 2026 · 1 fileMessage 70 · AdequateLow 40Details
Commit message · Nicolas Dorier
Fix: Server not recovering after a plugin crash (#7335)
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Low 40/100
This commit fixes a bug where BTCPay Server would not properly recover after a plugin crashed. The server tries to identify which plugin caused an exception by looking at the stack trace. The old code only checked the main assembly name and did not look inside nested/inner exceptions, so it sometimes failed to find the culprit plugin. The fix makes the search walk through inner exceptions and also maps all assemblies loaded by each plugin, not just the plugin's primary assembly. A second small fix prevents malformed plugin commands from crashing the command parser.
AI review queuedfix(API): add storeId-less routes for invoices, payment requests, and pull payments (#7313)by Abhijay Jain · ad6fa344 · Apr 24, 2026 · 21 filesMessage 70 · AdequateModerate 51Details
Commit message · Abhijay Jain
fix(API): add storeId-less routes for invoices, payment requests, and pull payments (#7313)
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Moderate 51/100
This commit changes several BTCPay Server API endpoints so that callers no longer need to supply a store ID when working with existing invoices, payment requests, and pull payments. The server now looks up the store automatically from the invoice/payment-request/pull-payment record. The old store-scoped routes are kept alongside the new shorter routes. The change is described as a convenience/cleanup fix, not as a security patch, and the diff does not show any new authorization checks being added.
AI review queuedImprove test speedby Nicolas Dorier · 53b85dd2 · Apr 23, 2026 · 3 filesMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Improve test speed
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only changes test configuration files for the BTCPay Server project. It adds the Bitcoin setting `unsafesqlitesync=1` to the docker-compose files used during automated testing. This setting makes test execution faster by relaxing how safely Bitcoin Core writes its SQLite wallet data to disk. It does not affect production BTCPay Server code or live deployments, and there is no indication it fixes or introduces a security vulnerability.
AI review queuedFix buildby Nicolas Dorier · 08f13ad9 · Apr 21, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix build
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit fixes a typo in a package version number. The version string for the NBXplorer.Client package had an extra stray backtick character (`), which would break the build. Removing the backtick restores the intended version 5.0.6 and allows the project to compile normally. There is no security issue here.
AI review queuedUpdate translationsby Nicolas Dorier · 784e5df0 · Apr 21, 2026 · 2 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update translations
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine translation and localization update. It adds, removes, and updates user-visible text strings in BTCPay Server. There is no code logic change, no security fix, and no vulnerability introduced in the diff itself.
AI review queuedbump nbxby Nicolas Dorier · a5e7f7a0 · Apr 21, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
bump nbx
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply updates a software dependency (NBXplorer.Client) from version 5.0.5 to 5.0.6. There is no information in the commit itself about what changed in the new version or whether it fixes any security issue. Based only on this diff, no security problem can be identified.
AI review queuedbump libsby Nicolas Dorier · 509c86c6 · Apr 21, 2026 · 7 filesMessage 0 · OpaqueLow 25Details
Commit message · Nicolas Dorier
bump libs
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 25/100
This commit updates several third-party software libraries and Docker base images to newer patch versions. It does not change BTCPay Server's own code. Such updates are routine maintenance and often include bug fixes or security fixes from upstream vendors, but the commit message gives no specific security reason and no vulnerability details are visible in the diff.
AI review queuedBump 2.3.8by Nicolas Dorier · 28fa4f44 · Apr 21, 2026 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Bump 2.3.8
0/100 · OpaqueMessage clarity
! Very short subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine version bump from 2.3.7 to 2.3.8. It only updates the version number and the changelog. There are no code changes that fix or introduce any security issue in this commit itself.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Low 49/100
This commit refactors an existing "login code" feature into a new optional plugin called Impersonation. The feature lets an already-logged-in user generate a short-lived QR code/login code that can be used on another device to sign in as the same user. The commit adds a new permission, btcpay.impersonation.canimpersonate, and rules that try to limit impersonation: a user can impersonate themselves, and server admins can impersonate non-admin users but not other admins. The code is a refactor rather than a reported vulnerability fix, but it moves a sensitive authentication capability behind a plugin and a permission check, which is a security-relevant design change.