BT
← All projectsBTCPay Server

BTCPay Server

Free, open-source, self-hosted Bitcoin payment processor supporting on-chain and Lightning payments.

BitcoinLightning NetworkPayment infrastructureNormal
Repository coverage

977 commits in the local evidence base

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.

125security candidates288second-pass queue413AI analyses
168commits · 30 days
317commits · 60 days
557commits · 180 days
897commits · 365 days
Backfill bands
Aug 8 → Feb 9247 seen22 candidatesComplete
Feb 9 → Jun 9197 seen39 candidatesComplete
Jun 9 → Jul 954 seen0 candidatesComplete
Jul 9 → Aug 865 seen16 candidatesComplete
Commit communication

Does the history explain itself?

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
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Nicolas Dorier676793111048
Cerberus622290
Andrew Camilleri (Kukks)2233148
Andrew Camilleri1325160
ndeet111133
Chukwuleta Tobechi33714066
rockstardev33612049
Abhijay Jain26610087
thgO.O32512066
dstrukt726061
Tim522074
tumutech222067
Analysis record

Published AI watches

Last scanned 36 minutes ago

Informational 15 AI analysisMessage 18 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Rename attribute

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.

5854d8a3by Nicolas Dorier+24−2411 files
No security note in commit
Informational 19 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Use server translations on the invoice checkout page (#7828)

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
bb14f177by Chukwuleta Tobechi+219−585290 files
No security note in commit
Informational 12 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update dependency and .NET 10 servicing images (#7831)

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…

Patch-level .NET runtime/SDK image update (potential servicing fixes, unspecified)Patch-level third-party NuGet package update (CsvHelper 34.0.0 -> 34.1.0, unspecified reason)
d5ecad56by Nicolas Dorier+4−43 files
No security note in commit
High 78 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Harden account and payment handling

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
Vendor flagged security relevance
Informational 19 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Translate remaining public pages and remove invoice checkout language option (#7815)

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 …

1ab0a206by Chukwuleta Tobechi+122−9819 files
No security note in commit
Low 47 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7780 from tumutech/fix-inventory-counts

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
0ba97eacby Nicolas Dorier+187−1611 files
No security note in commit
Low 44 AI analysisMessage 83 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix duplicate inventory returns when expired invoices are marked invalid

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
6d4beac4by tumutech+187−1611 files
No security note in commit
Informational 24 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Apply store’s language on customer-facing pages (#7656)

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
55d71e89by Chukwuleta Tobechi+449−10422 files
No security note in commit
Low 29 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7810 from efeesrefinal/fix/wallet-transaction-filters

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
867209d1by Nicolas Dorier+27−93 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Bump LND to v0.21.8-beta

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…

4bcdc689by r1ckstardev+8−84 files
No security note in commit
Informational 11 AI analysisMessage 35 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update NuGet dependencies

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…

9951be68by AlfredTheBot69+3−32 files
No security note in commit
Low 34 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update NuGet dependencies and compatibility

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
bef0935cby Alfred+55−4411 files
No security note in commit
Informational 24 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7795 from tumutech/fix-api-key-permission-usage-analysis

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
c9a45b12by Nicolas Dorier+128−484 files
No security note in commit
Informational 22 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix API key View Usage crash with multi-store permission usage

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
0ade56dfby tumutech+128−484 files
No security note in commit
Moderate 51 AI analysisMessage 81 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix RoundToSignificant for negative amounts (#7782)

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
6899974aby Amartya Vikram Singh+30−23 files
No security note in commit
Low 49 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix missing command in API key authorization

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
0f31ef51by Nicolas Dorier+1−11 file
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7610 from TChukwuleta/ft/manifest-redirect-bcp47

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
381ad1f0by Nicolas Dorier+223−393 files
No security note in commit
Moderate 60 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Support translation repository redirects and BCP 47 identifiers

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
896299cdby Chukwuleta Tobechi+223−393 files
Vendor flagged security relevance
Low 29 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7781 from NicolasDorier/cleanup-pre-1.12-migrations

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
9fbfc6c5by Nicolas Dorier+542−275243 files
No security note in commit
Low 34 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Remove migrations prior to BTCPay Server 1.12.0

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
57234d0eby Nicolas Dorier+542−275243 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedFix flay Payjoin testsby Nicolas Dorier · 2306242d · Jan 27, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flay Payjoin tests

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 an automated UI test file. It adds a helper that checks whether a Bitcoin payment address was correctly filled in after clicking a parse button, and inserts that check plus a screenshot step at three points in the test. There is no change to production code, no user-facing behavior change, and no security fix.

AI review queuedImprove pgpkey verifby Nicolas Dorier · b4beebd3 · Jan 27, 2026 · 1 fileMessage 28 · OpaqueInformational 12Details
Commit message · Nicolas Dorier

Improve pgpkey verif

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit tightens a CI script that checks whether Git commits are cryptographically signed. Previously, the script only rejected commits with status 'N' (no signature). Now it accepts only 'G' (valid trusted signature) or 'U' (valid but untrusted signature) and rejects everything else. This is a hardening improvement, not a fix for an active security flaw.

AI review queuedRestore CheckDefaultTranslationsUpToDateby Nicolas Dorier · aedc9f3a · Jan 27, 2026 · 1 fileMessage 25 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Restore CheckDefaultTranslationsUpToDate

25/100 · OpaqueMessage clarity
✓ Descriptive 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 restores a test that checks whether the project's default translation file is up to date before a release. It does not change production code, fix a bug, or alter security behavior. It is purely a quality-assurance test for translation data.

AI review queuedUpdate translationsby Nicolas Dorier · c5bede1b · Jan 27, 2026 · 1 fileMessage 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
translation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds new translation strings (empty placeholder entries for future localization) to a single C# file. There are no code logic changes, no security fixes, and no functional behavior changes.

AI review queuedChangelog 2.3.4by Nicolas Dorier · 3865a4d3 · Jan 27, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Changelog 2.3.4

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 is a routine version bump and changelog update for BTCPay Server 2.3.4. It does not change any application code, only records what changed in the release. There is nothing in the diff that introduces or fixes a security issue by itself.

AI review queuedAdd deliveryTime to APIby Nicolas Dorier · 9563e90c · Jan 27, 2026 · 4 filesMessage 28 · OpaqueInformational 18Details
Commit message · Nicolas Dorier

Add deliveryTime to API

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 adds a new 'deliveryTime' field to BTCPay Server's webhook API responses and updates the related documentation and invoice UI wording. It exposes when a webhook was actually sent, separate from when it was scheduled. There is no indication this change fixes or introduces a security vulnerability; it appears to be a transparency/usability improvement.

AI review queuedFix flaky testsby Nicolas Dorier · 3a09fae8 · Jan 26, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flaky tests

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 code. It replaces a few brittle checks in automated UI tests with more robust Playwright-style assertions and adds a page-load wait. There is no change to production code, no user-facing behavior change, and no security relevance.

Security candidateDo not show Server service links on the Dashboard if insuffient permissionsby Nicolas Dorier · f75cdf37 · Jan 26, 2026 · 5 filesMessage 50 · ThinLow 34Details
Commit message · Nicolas Dorier

Do not show Server service links on the Dashboard if insuffient permissions

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Low 34/100

This change hides a dashboard widget called 'Lightning Services' from users who do not have permission to change server settings. Previously, the widget may have been visible to users who lacked those rights, potentially exposing links or information about server-level Lightning services. The fix adds a permission check directly to the widget's HTML wrapper so it only renders for authorized users.

Security candidateFix: CanModifyInvoices permission should include the ability to see the lightning invoices of the storeby Nicolas Dorier · 8f7311bd · Jan 26, 2026 · 1 fileMessage 62 · AdequateModerate 50Details
Commit message · Nicolas Dorier

Fix: CanModifyInvoices permission should include the ability to see the lightning invoices of the store

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
credential or privilege state
AI analysis · Moderate 50/100

This commit fixes a permission inconsistency in BTCPay Server. Previously, a user who had permission to create Lightning invoices for a store might not have had explicit permission to view those same Lightning invoices. The change makes 'view Lightning invoice' a child permission of 'create Lightning invoice', so anyone who can create them can also see them. This is described as a fix, not a new security vulnerability disclosure, and the diff alone does not show an active exploit or a disclosed incident.

Security candidateAdd LUNO exchange as default for ZAR currencyby Nicolas Dorier · d27793dc · Jan 23, 2026 · 9 filesMessage 45 · ThinInformational 17Details
Commit message · Nicolas Dorier

Add LUNO exchange as default for ZAR currency

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 17/100

This commit mainly adds the LUNO exchange as the default source for South African Rand (ZAR) exchange rates in BTCPay Server. It also includes a small hardening fix in another rate provider so that missing bid/ask values don't crash the app, plus a batch of unrelated test reliability improvements. There is no clear security vulnerability being patched.

AI review queuedrefactor: Remove Selenium tests and testing infrastructureby Abhijay007 · b3d1a0a2 · Jan 21, 2026 · 18 filesMessage 87 · StrongInformational 15Details
Commit message · Abhijay007

refactor: Remove Selenium tests and testing infrastructure

Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>

87/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit removes the old Selenium browser-automation test suite and its supporting infrastructure from the BTCPay Server project. It deletes test files, package references, Docker services, and CI job definitions, and updates two comments in production view files that previously mentioned Selenium. There is no change to the actual application code that users interact with, and no security fix or vulnerability is introduced.

AI review queuedTests: Move tests to PullPaymentTests.csby Nicolas Dorier · 834fab4f · Jan 21, 2026 · 3 filesMessage 55 · ThinInformational 15Details
Commit message · Nicolas Dorier

Tests: Move tests to PullPaymentTests.cs

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is purely a test-code reorganization. It moves several Playwright UI tests from one test file to another and creates a new dedicated WalletTests.cs file. No production application code was changed, so it cannot introduce a security vulnerability in the software users run.

AI review queuedTests: Move WebhooksTests in the same classby Nicolas Dorier · f545a9b6 · Jan 21, 2026 · 6 filesMessage 55 · ThinInformational 15Details
Commit message · Nicolas Dorier

Tests: Move WebhooksTests in the same class

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a test-code refactoring: it moves existing webhook-related tests from several scattered test files into a single new file called WebhooksTests.cs. No production code is changed, and the commit message explicitly says it is just moving tests. There is no security fix or vulnerability here.

AI review queuedMake tests more reliableby Nicolas Dorier · 46e06266 · Jan 21, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Make tests more reliable

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 code in BTCPay Server's PlaywrightTests.cs. It refactors how browser tabs are switched during automated UI tests and replaces some polling-style assertions with more direct Playwright expectations. There is no change to production code, no security fix, and no user-facing behavior change.

Security candidateFix flaky CanCreateCrowdfundingAppby Nicolas Dorier · 69cc179f · Jan 21, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flaky CanCreateCrowdfundingApp

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
boot or update path
AI analysis · Informational 15/100

This commit fixes a flaky automated test for the crowdfunding feature. The test previously cleared a date field by directly manipulating the webpage's internal value, which was unreliable. The change makes the test click a visible 'Clear' button instead, and adds an ID to that button so the test can find it. There is no security issue here.

AI review queuedAvoid NRE in ErrorControllerby Nicolas Dorier · 6fade98a · Jan 20, 2026 · 1 fileMessage 35 · OpaqueLow 34Details
Commit message · Nicolas Dorier

Avoid NRE in ErrorController

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 34/100

This commit fixes a potential server crash in BTCPay Server's error-handling page. Previously, if a visitor requested a non-HTML error page without specifying a status code, the code could try to use a missing value and throw a NullReferenceException. The change supplies a fallback 500 status code and renames a loop variable to avoid shadowing. It is a small defensive fix rather than a clear-cut exploitable vulnerability.

Security candidateRefactor: Move PoS views in PoS plugin folderby Nicolas Dorier · e09133e0 · Jan 20, 2026 · 12 filesMessage 57 · ThinInformational 15Details
Commit message · Nicolas Dorier

Refactor: Move PoS views in PoS plugin folder

57/100 · ThinMessage clarity
✓ 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 pathboot or update path
AI analysis · Informational 15/100

This commit is a straightforward code reorganization: it moves the Point of Sale (PoS) user-interface files from a shared views folder into the dedicated Point of Sale plugin folder, and updates the corresponding file paths in the controller and plugin registration. There is no functional change to how the application behaves, and no security fix or vulnerability is introduced.

AI review queuedFix testby Nicolas Dorier · 29eaf670 · Jan 20, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix test

0/100 · OpaqueMessage clarity
✓ Mentions testing or verification! 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 changes a single character in a test file, flipping a comparison operator from '==' to '!='. It is a test-only fix that corrects the logic of an assertion checking whether a UI alert appears. There is no change to production code and no security relevance.

Security candidate[Feature] Store-scoped labels + linkedType-scoped LabelManager suggestions (#7050)by thgO.O · 689b9d17 · Jan 20, 2026 · 25 filesMessage 91 · StrongLow 29Details
Commit message · thgO.O

[Feature] Store-scoped labels + linkedType-scoped LabelManager suggestions (#7050)

* feat: allow label manager to scope suggestions by linked type

* fix: render unlabeled payment requests as "Unlabeled" in reports

* feat: apply linked type scoped labels to EditPaymentRequest view

* feat: add store-scoped label tables

* test: cover store-scoped label migration

* feat: add StoreLabelRepository

* feat: support store-scoped LabelManager

* refactor: payment requests use store-scoped labels

* fix: adapt ReservedAddresses to labelmanager event

* refactor: coderabbit nits

* refactor: type-scoped store labels schema with snake_case

* refactor: persist label colors as column

* refactor: cleanup label links and usage

* refactor: simplify label repository ops

* fix: secure label updates and ensure pgcrypto

* test: stabilize CanUpgradeAndDowngrade

* refactor: coderabbit nits

* feat: use snake_case schema and case-insensitive label merge

* test: add playwright coverage for store label casing

* refactor: use snake_case schema and indexed case-insensitive label lookups

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
update trustsigning or wallet path
AI analysis · Low 29/100

This commit refactors how BTCPay Server stores labels for payment requests, moving them from a wallet-based graph system into new store-scoped database tables. It also adds a new API endpoint for updating store-scoped labels. The changes are primarily a feature/refactoring effort, but they include security-relevant hardening such as CSRF token validation on the new update endpoint, a check that the target store exists and matches the route, and restrictions preventing deletion or renaming of reserved system label types. A migration copies existing payment-request labels into the new tables and removes the old wallet-graph entries.

AI review queuedfix: scan-qrcode icon alignment (#7116)by Carlos Marques · 36e2e6ee · Jan 20, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · Carlos Marques

fix: scan-qrcode icon alignment (#7116)

65/100 · AdequateMessage clarity
✓ 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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a purely cosmetic fix for a QR-code scan button icon in the wallet send page. It adjusts CSS margins and adds flexbox centering so the icon lines up correctly. There is no security relevance.

Security candidateRefactor: Move crowdfund files into Plugins/Crowdfund (#7112)by Nicolas Dorier · 757ad829 · Jan 16, 2026 · 8 filesMessage 70 · AdequateInformational 19Details
Commit message · Nicolas Dorier

Refactor: Move crowdfund files into Plugins/Crowdfund (#7112)

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
boot or update path
AI analysis · Informational 19/100

This commit is a code reorganization: it moves the Crowdfund feature's files into a dedicated plugin folder and updates the controller to use newer ASP.NET Core patterns (primary constructor, area routing). It also makes a small change so that looking up a store for an app throws an exception if the store is missing, instead of returning null. There is no clear security fix or vulnerability being patched here.

AI review queuedMove some tests in PullPaymentsTests, fix warningsby Nicolas Dorier · 3d7682b7 · Jan 16, 2026 · 9 filesMessage 60 · AdequateInformational 15Details
Commit message · Nicolas Dorier

Move some tests in PullPaymentsTests, fix warnings

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is purely a test-code refactor. It moves existing pull-payment and coin-selection tests into a new dedicated test file, removes duplicate copies from other test files, adds a couple of shared assertion helpers, and fixes compiler/style warnings. No production application code is changed, so it cannot affect the security of a running BTCPay Server instance.

AI review queuedTests: Split Playwrights tests (#7107)by Nicolas Dorier · ece54569 · Jan 16, 2026 · 8 filesMessage 63 · AdequateInformational 15Details
Commit message · Nicolas Dorier

Tests: Split Playwrights tests (#7107)

63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit reorganizes automated browser tests by splitting some Playwright tests into a second CI job. It does not change any production code, user-facing behavior, or security-sensitive logic. The only non-test code change is a small tolerance adjustment in a refund amount assertion, which is still a test-only change.

AI review queuedTests: Port CanTranslateLoginPage to playwright (#7106)by Nicolas Dorier · 3f52aa7f · Jan 15, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · Nicolas Dorier

Tests: Port CanTranslateLoginPage to playwright (#7106)

68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine test modernization: it rewrites one existing automated UI test to use the Playwright testing framework instead of Selenium, and adds a single HTML data-testid attribute to the signed-out page header so the test can reliably locate it. There is no change to production logic, no security fix, and no vulnerability introduced.

AI review queuedTry fix flakyby Nicolas Dorier · 1b86265c · Jan 14, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Try fix flaky

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 only changes the order of steps in an automated test script for the BTCPay Server project. It moves a 'Description Edit' step earlier in the test flow to try to fix a flaky (unreliable) test. There is no change to production code, no user-facing behavior change, and no security relevance.