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 queuedTest fix, ui nitby rockstardev · 77a914f0 · Dec 17, 2025 · 5 filesMessage 38 · OpaqueInformational 16Details
Commit message · rockstardev
Test fix, ui nit
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 16/100
This commit is a routine test and UI cleanup. It reworks how old payment-request data is migrated into newer database columns, adds null checks so missing fields don't crash, and changes a table header from 'Reference Id' to 'Id'. There is no direct evidence of an exploitable security bug in the diff.
AI review queuedSupport for editing labelsby rockstardev · 4817654b · Dec 17, 2025 · 5 filesMessage 35 · OpaqueInformational 22Details
Commit message · rockstardev
Support for editing labels
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 22/100
This commit adds a new feature that lets users rename labels attached to wallets and payment requests. It introduces new web forms, controller actions, and a database rename routine. The change is a feature addition, not a documented security fix. There is one notable design quirk: the wallet-label edit action does not show an explicit authorization attribute in the diff, while the payment-request edit action does. That could simply be because wallet routes already inherit authorization from the controller, but the diff alone does not prove it, so it should be treated as a low-confidence observation rather than a confirmed vulnerability.
AI review queuedrefactor: improve amount search, wallet label query and label manager icon URLby thgO.O · 276e39c1 · Dec 17, 2025 · 3 filesMessage 62 · AdequateLow 28Details
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 28/100
This commit is a code cleanup/refactor touching three areas: payment-request search, wallet label lookup, and a label-manager icon URL. The most notable change is that the payment-request search no longer compares the user's search text directly against the database's Amount column as text; instead it tries to parse the search text as a decimal number and, if successful, compares it numerically. The wallet-label query is rewritten from LINQ to raw SQL. The JavaScript change fixes an icon path to use a configurable base URL and removes an explicit 'credentials: include' flag from a fetch call. None of these changes, on their own, look like a clear security fix, but the removal of the text-based amount comparison and the credentials flag are worth noting.
AI review queuedrefactor: optimize payment request labels loading and reportingby thgO.O · 57c98283 · Dec 17, 2025 · 4 filesMessage 62 · AdequateInformational 19Details
Commit message · thgO.O
refactor: optimize payment request labels loading and reporting
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit is a performance refactor, not a security fix. It replaces many individual database lookups for payment-request labels with a single batched lookup, and makes a couple of minor cleanups (removing a comment, using a switch expression). There is no indication it changes any security boundary or fixes a vulnerability.
AI review queuedrefactor: improve label manager caching and refreshby thgO.O · 99eb9f00 · Dec 17, 2025 · 2 filesMessage 62 · AdequateInformational 13Details
Commit message · thgO.O
refactor: improve label manager caching and refresh
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 13/100
This commit is a routine code cleanup of the wallet address label picker in BTCPay Server. It rewrites how the page caches and refreshes the list of available labels, removes an old Vue.js event listener, and adds a guard so the script does nothing if the expected HTML element is missing. There is no clear security bug being fixed and no security relevance is stated by the project.
AI review queuedfeat: improve payment requests listing, filters and reportingby thgO.O · adf5f3d9 · Dec 17, 2025 · 8 filesMessage 62 · AdequateInformational 17Details
Commit message · thgO.O
feat: improve payment requests listing, filters and reporting
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit adds new UI filters, a label system, and a reporting provider for payment requests. It also changes the search query to use a hand-written SQL statement. The change is described as a feature improvement, not a security fix. The SQL query uses Entity Framework's parameterized raw SQL, which generally protects against SQL injection, but the code mixes raw SQL with LINQ and introduces a new label-filtering path. There is no direct evidence in the commit of a vulnerability being fixed or introduced, but the raw SQL and label-filtering logic are worth reviewing carefully because mistakes in those areas can lead to security bugs.
AI review queuedfix: reserved addresses label filtering after label changes and initLabelManager errorby thgO.O · fb3e9cc9 · Dec 17, 2025 · 2 filesMessage 62 · AdequateInformational 23Details
Commit message · thgO.O
fix: reserved addresses label filtering after label changes and initLabelManager error
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 23/100
This commit fixes a UI bug in BTCPay Server's wallet address list. Previously, when a user changed labels on a reserved Bitcoin address, the label filter on the page did not update to reflect the new labels, and an error in the label manager initialization could break the feature. The patch makes the address list listen for label-change events and refresh its internal label data so filtering works correctly after edits.
AI review queuedFix docker-composeby Nicolas Dorier · 0853900a · Dec 17, 2025 · 3 filesMessage 28 · OpaqueInformational 18Details
Commit message · Nicolas Dorier
Fix docker-compose
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 18/100
This commit updates test-only Docker configuration files. It upgrades the PostgreSQL database image used in automated testing from version 13.13 to 18.1, fixes indentation, and adds a persistent data volume for the test database. These files are part of the project's internal test harness and are not used in production deployments. There is no direct security fix or vulnerability being patched here.
AI review queuedbump postgresby Nicolas Dorier · 2c64f037 · Dec 17, 2025 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
bump postgres
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 updates the PostgreSQL database version used only in BTCPay Server's automated test environment from version 13.23 to 18.1. It also changes the data directory mount path inside the container. There is no indication this affects production systems or fixes a security vulnerability.
AI review queuedbump postgresby Nicolas Dorier · 9e067d11 · Dec 17, 2025 · 1 fileMessage 18 · OpaqueInformational 17Details
Commit message · Nicolas Dorier
bump postgres
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 17/100
This commit updates the PostgreSQL database version used only in BTCPay Server's automated test environment from 13.13 to 13.23, and adds a persistent data volume for that test database. It does not change production code. The newer PostgreSQL patch release likely fixes bugs and security issues in the database software itself, but the commit does not address any vulnerability in BTCPay Server's own code.
AI review queuedAdd publish-docker.shby Nicolas Dorier · 2a5ad7c2 · Dec 17, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Add publish-docker.sh
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit adds a simple shell script used by BTCPay Server maintainers to automate creating and pushing a Git version tag when publishing Docker images. It does not change application code, user-facing behavior, or any security-sensitive logic. There is nothing in the commit that introduces a vulnerability or fixes one.
AI review queuedWebhookTriggerProviders can by asyncby Nicolas Dorier · 3097860f · Dec 15, 2025 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
WebhookTriggerProviders can by async
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine code refactor that lets webhook event providers run their lookup logic asynchronously. It changes a synchronous method to an async one and updates callers to await it. There is no security issue visible in the diff.
AI review queuedFix flaky CanMonetizeTestby Nicolas Dorier · 04d31b26 · Dec 10, 2025 · 2 filesMessage 35 · OpaqueInformational 23Details
Commit message · Nicolas Dorier
Fix flaky CanMonetizeTest
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 23/100
This commit fixes a flaky automated test for BTCPay Server's subscription/monetization feature. The code change removes a guard that previously prevented a subscriber's plan from being restarted if it had already started. The test change waits for a background activation event and reloads the page before checking the UI. On its own, the patch looks like a timing/test-stability fix rather than a clear security fix, but removing the 'already started' guard could, in theory, allow duplicate plan activations or repeated credits if the event handler runs more than once.
Security candidate[Greenfield] Subscription API (#7022)by Nicolas Dorier · 1d3cb757 · Dec 9, 2025 · 48 filesMessage 43 · ThinLow 37Details
Commit message · Nicolas Dorier
[Greenfield] Subscription API (#7022)
43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
boot or update pathauthentication path
AI analysis · Low 37/100
This commit introduces a new Greenfield (REST) Subscription API to BTCPay Server, allowing stores to manage subscription offerings, plans, subscribers, credits, and checkout sessions programmatically. It also refactors existing subscription internals, adds new permissions, and makes small related fixes such as handling empty URL paths and adding a null check for invoice IDs. There is no explicit security bug in the diff, but the large new attack surface and a few design choices warrant careful review.
Security candidateRename permissions for offerings (#7021)by Nicolas Dorier · 58c5e9cd · Dec 5, 2025 · 6 filesMessage 53 · ThinInformational 15Details
Commit message · Nicolas Dorier
Rename permissions for offerings (#7021)
53/100 · ThinMessage clarity
✓ 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 state
AI analysis · Informational 15/100
This commit simply renames two permission strings from 'membership' to 'offerings' across the codebase. It is a non-functional refactor that updates labels, constants, authorization checks, and API documentation to match the new terminology. There is no security-relevant change.
AI review queuedpage-primary should not be automatically translatedby Nicolas Dorier · ed082c55 · Dec 3, 2025 · 35 filesMessage 50 · ThinInformational 15Details
Commit message · Nicolas Dorier
page-primary should not be automatically translated
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! 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 is a user-interface localization cleanup, not a security fix. It stops the system from automatically translating any button or link with the ID 'page-primary'. Instead, developers must now explicitly mark each primary button/link with a 'text-translate' attribute if they want it translated. The commit adds that attribute to many existing buttons and links so translations continue to work as intended. There is no security vulnerability here.
AI review queuedRename Entitlement -> Feature (#7016)by Nicolas Dorier · fa314d2f · Dec 2, 2025 · 29 filesMessage 43 · ThinInformational 15Details
Commit message · Nicolas Dorier
Rename Entitlement -> Feature (#7016)
43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 15/100
This commit is a straightforward internal rename from the word 'Entitlement' to the word 'Feature' across the new subscriptions/monetization plugin code. It changes class names, database table names, property names, method names, UI labels, and test helpers, but does not alter any security logic, access checks, or data handling behavior. There is no indication this fixes or introduces a security issue.
Security candidate[Feature] Monetization (#6986)by Nicolas Dorier · bcb5c56b · Dec 2, 2025 · 97 filesMessage 43 · ThinLow 40Details
Commit message · Nicolas Dorier
[Feature] Monetization (#6986)
43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 40/100
This is a large feature commit titled 'Monetization' that adds subscription and paid-access functionality to BTCPay Server. It introduces new plugins for monetization and subscriptions, changes how user login restrictions are enforced, adds a 'limited login' authentication scheme, and refactors user registration/invitation email flows. The changes touch authentication, authorization, billing, and user lifecycle logic. While the commit is framed as a feature, several areas have security implications: a new limited-login path that signs users in under a separate scheme when normal login is blocked, changes to password-reset and invitation-token handling, and new database entities for plans/subscribers/portal sessions. No explicit security bug is visible in the diff, but the breadth and sensitivity of the modified code means defects could have significant consequences.
AI review queuedFix property name: use CanUseHotWallet and CanCreateNewColdWalletby psam21 · cf692c6e · Nov 24, 2025 · 1 fileMessage 50 · ThinLow 29Details
Commit message · psam21
Fix property name: use CanUseHotWallet and CanCreateNewColdWallet
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100
This is a tiny one-line fix in a BTCPay Server web page that checks whether a user is allowed to set up certain types of cryptocurrency wallets. The old code referenced two properties that appear to have been renamed or replaced. The change simply swaps in the current property names so the page renders the wallet-setup section correctly. It is most likely a routine bug fix, but because it touches permission checks for wallet creation, it could have security-adjacent effects if the wrong users were shown (or hidden from) wallet options.
Hide wallet creation option when permissions disabled
- Pass wallet creation permissions to SetupWallet view - Conditionally render 'Create a new wallet' based on CanCreateHotWallet || CanCreateWalletWatchOnly - Remove 'I have a wallet' and 'I don't have a wallet' section headings - Always show 'Connect an existing wallet' option (import is always allowed)
Fixes #6991
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
credential or privilege statesigning or wallet path
AI analysis · Low 40/100
This commit fixes a UI bug where BTCPay Server was showing a 'Create a new wallet' button to users who did not have permission to create wallets. The button itself was just a link; the actual wallet creation endpoint still enforced permissions separately. So the fix is about hiding an option that shouldn't appear, not about blocking an unauthorized action. It is a defense-in-depth or user-experience security improvement rather than a critical vulnerability.
AI review queuedFix missing assignationby Nicolas Dorier · 0a518320 · Nov 21, 2025 · 1 fileMessage 28 · OpaqueLow 34Details
Commit message · Nicolas Dorier
Fix missing assignation
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 34/100
This commit fixes a simple but potentially important coding mistake: a constructor parameter named `loadAssembliesInDefaultLoadContext` was not being saved into its matching field. As a result, the plugin loader's intended setting about where to load assemblies was effectively ignored, and the code would fall back to the default value (false). This could change how plugins are isolated from the main application, potentially weakening the sandbox between plugins and the host.
AI review queuedFix flacky CanUseFormsby Nicolas Dorier · 4e34a185 · Nov 21, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix flacky CanUseForms
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit fixes a flaky automated test, not a security issue. The test previously checked the entire web page content for an email address, which could fail if the email appeared anywhere else on the page or if timing caused the page content to be incomplete. The change narrows the check to look specifically at the value of the email input field. There is no indication this affects real users or production code.
AI review queuedImprove testby Nicolas Dorier · 6b76af43 · Nov 18, 2025 · 6 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Improve test
28/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! 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 test and code-quality improvement. It tightens a test helper that was incorrectly always setting IsAdmin to true, modernizes some C# syntax, removes unused imports, and adds test-id attributes to a web page so automated tests can locate elements more reliably. There is no security-relevant change to production behavior.
AI review queuedRemove LocalBTCPayClientby Nicolas Dorier · ccbc0614 · Nov 18, 2025 · 4 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Remove LocalBTCPayClient
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 removes an internal-only API client called LocalBTCPayClient. It was a convenience wrapper that let server code call BTCPay Server's own Greenfield API without making real HTTP requests. There is no indication this change fixes a security vulnerability; it appears to be a code cleanup or architectural simplification.
Security candidateFeature: Plugin can extend whether an account can login or notby Nicolas Dorier · 41f55882 · Nov 14, 2025 · 13 filesMessage 50 · ThinLow 37Details
Commit message · Nicolas Dorier
Feature: Plugin can extend whether an account can login or not
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 37/100
This commit refactors how BTCPay Server decides whether a user is allowed to log in. It replaces a simple built-in check with a new extensible system where plugins can add their own login-blocking rules. The change touches password logins, two-factor/FIDO2/LNURL logins, API key authentication, and basic HTTP authentication. It also fixes a small bug in basic authentication where the password was checked before the user was validated. There is no claim in the commit that this fixes a known security vulnerability, and no CVE or advisory is referenced.