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 35 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.

Security candidateInclude witness UTXOs in SegWit PSBTsby rockstardev · 63236df4 · Jul 30, 2026 · 4 filesMessage 45 · ThinLow 45Details
Commit message · rockstardev

Include witness UTXOs in SegWit PSBTs

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 45/100

This commit changes BTCPay Server so that when it builds or decodes Partially Signed Bitcoin Transactions (PSBTs), it explicitly adds a compact 'witness UTXO' record for any SegWit inputs. Previously, some SegWit PSBTs may only have carried the full previous transaction (non-witness UTXO). Adding the witness UTXO improves compatibility with hardware wallets and signers that require or prefer it, and can reduce the data those devices need to process. The change itself is a correctness/compatibility improvement rather than an obvious vulnerability fix, but the absence of witness UTXOs in SegWit PSBTs can cause signing failures or force fallback behaviour in some wallets.

Security candidateAddress pending signature retry review feedbackby rockstardev · 89b8f49c · Jul 29, 2026 · 2 filesMessage 50 · ThinLow 26Details
Commit message · rockstardev

Address pending signature retry review feedback

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 26/100

This commit is a follow-up code review patch for BTCPay Server's pending Bitcoin transaction (multisig) signing feature. It tightens when the service logs a warning versus a debug message after a failed finalization attempt, and it removes an unused optional parameter from an internal helper method. The changes are defensive: they reduce false-warning noise and make the per-input signature tracking more accurate. There is no direct evidence in the commit of an exploitable vulnerability being fixed.

AI review queuedSimplify pending finalization failure logsby rockstardev · 7e71c45e · Jul 28, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · rockstardev

Simplify pending finalization failure logs

45/100 · ThinMessage clarity
✓ 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 · Informational 15/100

This commit is a minor code cleanup that simplifies how BTCPay Server writes log messages when a pending multi-signature transaction fails to finalize. It removes the list of failed input indexes from the log and merges two nearly identical log statements into one. There is no security-relevant change.

Security candidateBound pending multisig signature historyby rockstardev · eb0f15ca · Jul 28, 2026 · 2 filesMessage 50 · ThinLow 35Details
Commit message · rockstardev

Bound pending multisig signature history

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 35/100

This change tightens how BTCPay Server stores signature attempts for multi-signature Bitcoin transactions. Previously, every submitted PSBT (a partially signed transaction file) was kept in history, even if it added no real progress. Now only PSBTs that actually advance signing or successfully finalize the transaction are retained. This prevents unbounded growth of stored signature history, which could waste storage and potentially be abused to clutter or inflate a pending transaction record.

AI review queuedLog pending transaction finalization errorsby rockstardev · c3fe1d7b · Jul 28, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · rockstardev

Log pending transaction finalization errors

45/100 · ThinMessage clarity
✓ 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 · Informational 15/100

This commit only adds more detailed logging when a pending multi-signature Bitcoin transaction fails to finalize. It does not change how transactions are validated, authorized, or executed. There is no security vulnerability being fixed here; it is purely an observability improvement for operators.

Security candidateFix pending multisig signature retriesby rockstardev · ebeafc5a · Jul 28, 2026 · 2 filesMessage 50 · ThinLow 42Details
Commit message · rockstardev

Fix pending multisig signature retries

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 42/100

This commit fixes a bug in BTCPay Server's multisig transaction handling. Previously, the service could get stuck in a 'Pending' state even when enough valid signatures had been collected, because it discarded new signature submissions that didn't immediately improve progress and didn't retry finalizing the transaction. The fix keeps distinct-but-not-yet-helpful PSBTs (partially signed transactions), records them, and retries finalization each time a new PSBT arrives, allowing later valid signatures to complete the transaction.

AI review queuedFix typoby Nicolas Dorier · 2ed0fa17 · Jul 22, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix typo

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit changes one word in the project's changelog, adding the word 'the' to a bullet point. It is a grammatical typo fix with no effect on software behavior, security, or user data.

Security candidateAdd race condition safe InvoiceRepository.UpdateMetadata (#7475)by Nicolas Dorier · 5664bd41 · Jul 22, 2026 · 10 filesMessage 58 · ThinLow 40Details
Commit message · Nicolas Dorier

Add race condition safe InvoiceRepository.UpdateMetadata (#7475)

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

This commit changes how BTCPay Server stores invoice comments and metadata. Previously, comments were saved in a separate field and could be updated with a method that was not safe when multiple requests happened at the same time. The patch moves comments into the invoice metadata and uses database-level JSON operations to update only the requested field, reducing the chance that simultaneous updates overwrite each other. It also removes the dedicated 'comment' field from the public API, so comments can only be updated through the UI or via metadata. The commit title explicitly calls this a race-condition safety fix.

AI review queuedBump anglesharp (#7476)by Nicolas Dorier · 4b914484 · Jul 22, 2026 · 1 fileMessage 36 · OpaqueLow 25Details
Commit message · Nicolas Dorier

Bump anglesharp (#7476)

36/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 25/100

This commit adds a direct package reference to AngleSharp version 1.5.2 in one of BTCPay Server's project files. AngleSharp is a library for parsing HTML and other markup. The change itself is a dependency bump/addition, but the commit message and diff do not explain why it was needed or whether it fixes a security issue. Without additional context, we cannot tell if this is a routine maintenance update or a response to a known vulnerability.

AI review queuedbump HtmlSanitizerby Nicolas Dorier · 41115cd3 · Jul 22, 2026 · 1 fileMessage 18 · OpaqueLow 46Details
Commit message · Nicolas Dorier

bump HtmlSanitizer

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
defensive validationsecond-pass: opaque commit message
AI analysis · Low 46/100

This commit updates the HtmlSanitizer software library from version 9.0.892 to 9.0.967. HtmlSanitizer is used to clean untrusted HTML and prevent malicious content from being displayed. Version bumps of this kind are often done to fix security bugs in the library, but the commit itself does not say what changed between these versions or whether any vulnerability affects BTCPay Server.

AI review queuedbump dotnetby Nicolas Dorier · 70257821 · Jul 21, 2026 · 7 filesMessage 0 · OpaqueLow 30Details
Commit message · Nicolas Dorier

bump dotnet

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 30/100

This commit updates the .NET runtime and several Microsoft packages from version 10.0.8/10.0.9 to 10.0.10, plus a couple of minor library updates. It is a routine dependency bump with no code changes. The commit message gives no security reason for the update, and no public references link it to any known vulnerability. Such updates often include undisclosed bug and security fixes in the underlying framework, so the change is security-relevant in a general maintenance sense, but there is no direct evidence this patch fixes a specific exploitable flaw in BTCPay Server.

AI review queuedbump depsby Nicolas Dorier · 949ed3a1 · Jul 21, 2026 · 5 filesMessage 0 · OpaqueLow 25Details
Commit message · Nicolas Dorier

bump deps

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 simply updates several third-party software libraries (dependencies) to newer patch versions. It does not change BTCPay Server's own code. Dependency bumps can fix hidden security bugs in those libraries, but the commit message gives no details, and no security advisory was supplied. On its own, this looks like routine maintenance rather than a confirmed security fix.

AI review queuedUpdate Changelogby Nicolas Dorier · 926b87b9 · Jul 18, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Update Changelog

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only edits the project's Changelog.md file, adding two missing entries that describe fixes already made elsewhere. There are no code changes in this commit itself, so it cannot introduce or fix any security issue directly.

AI review queuedSmall fixupby Nicolas Dorier · 25ac35c7 · Jul 17, 2026 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Small fixup

0/100 · OpaqueMessage clarity
! Very short subject! 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 minor cleanup: it changes how an 'empty transactions' message is created on a wallet page. Previously the message was stored as a chunk of HTML in translation files; now it is built safely in code with plain text. There is no security issue here—just a small improvement in how the page is assembled.

AI review queuedupdate translationsby Nicolas Dorier · a27f7a9a · Jul 17, 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 updates the list of translatable text strings in BTCPay Server. It adds, removes, and reorders phrases used by the application's user interface. There are no code logic changes, no security fixes, and no behavior changes.

AI review queuedSmall cleanupby Nicolas Dorier · 1dafff87 · Jul 17, 2026 · 1 fileMessage 18 · OpaqueModerate 65Details
Commit message · Nicolas Dorier

Small cleanup

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 · Moderate 65/100

This commit removes code that restricted cross-frame messaging to a specific trusted website origin. It now allows messages from any origin ('*') when sending, and only accepts messages from frames with an 'opaque' (null) origin when receiving. This appears to be a security cleanup that reduces the risk of malicious plugin frames tricking the host into trusting their origin, but the change is partial and the full context is unclear without more references.

Security candidatefeat: embed plugin directory in plugin management (#7381)by thgO.O · 5da26940 · Jul 17, 2026 · 29 filesMessage 70 · AdequateLow 38Details
Commit message · thgO.O

feat: embed plugin directory in plugin management (#7381)

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 · Low 38/100

This commit refactors BTCPay Server's plugin management into a dedicated plugin and adds an embedded plugin directory that loads content from an external plugin catalog via an iframe. The change moves plugin URLs from the server settings area to a new plugin area, adds URL sanitization for author and documentation links, and introduces checks to prevent installing mismatched plugin identifiers. It is a feature/refactoring commit rather than a disclosed security fix, though it includes some defensive hardening.

AI review queuedSmall code style suggestionby Nicolas Dorier · dfdbea93 · Jul 17, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Small code style suggestion

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 only changes a code style setting in the project's .editorconfig file. It tells developers to prefer shorter expression-bodied method syntax when it fits on one line. There is no functional code change, no bug fix, and no security relevance.

Security candidateAdd BIP-329 wallet label import (#7457)by Atharva Borade · 856967c3 · Jul 16, 2026 · 7 filesMessage 53 · ThinInformational 21Details
Commit message · Atharva Borade

Add BIP-329 wallet label import (#7457)

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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 21/100

This commit adds a feature that lets BTCPay Server users import wallet labels from a BIP-329 file. The code parses uploaded JSONL files, validates entries, and attaches labels to transactions, addresses, or transaction outputs. The change is a normal feature addition; there is no direct evidence in the commit that it fixes a security vulnerability, but it does introduce a new file-upload and parsing path that should be reviewed for robustness.

Security candidatefeat : add rtl language support with custom css (#7428)by Tim · 8ba284ce · Jul 15, 2026 · 11 filesMessage 58 · ThinInformational 15Details
Commit message · Tim

feat : add rtl language support with custom css (#7428)

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

This commit adds right-to-left (RTL) language support to BTCPay Server. It introduces metadata tracking for whether a language is RTL, fetches that flag from the translation manifest, stores it in the database, and switches the user interface to RTL-specific CSS stylesheets when an RTL language like Arabic is active. There is no security issue visible in the change.

Security candidateRename <vc:breadcrumb> (#7456)by Nicolas Dorier · 7d206d93 · Jul 14, 2026 · 106 filesMessage 43 · ThinInformational 15Details
Commit message · Nicolas Dorier

Rename <vc:breadcrumb> (#7456)

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 pathboot or update pathauthentication path
AI analysis · Informational 15/100

This commit is a routine UI refactor: it renames the internal ASP.NET Core view component from <vc:breadcrumb> to <vc:title-header>, updates CSS class names, and standardizes how page titles are set across many Razor views. There is no security-relevant change in behavior—no new endpoints, no permission changes, no input handling changes, and no fixes for injection or bypass issues.

Security candidateRefactor breadcrumb (#7455)by Nicolas Dorier · eac04593 · Jul 14, 2026 · 47 filesMessage 43 · ThinInformational 15Details
Commit message · Nicolas Dorier

Refactor breadcrumb (#7455)

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 pathauthentication path
AI analysis · Informational 15/100

This commit is a routine user-interface cleanup. It replaces many copies of hand-written breadcrumb navigation HTML across the application with a single shared 'Breadcrumb' view component. There is no security-relevant change here—only the way page headers and navigation links are rendered.

AI review queuedAdd agent skills (#7454)by Nicolas Dorier · 66fb6426 · Jul 14, 2026 · 6 filesMessage 36 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Add agent skills (#7454)

36/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit reorganizes internal documentation for AI coding assistants. It moves existing developer guidance from one file into separate 'skill' files and adds new style guides for frontend naming and test writing. No application code, configuration, or user-facing behavior was changed.

AI review queuedAdd SearchFiltersPMO to avoid repeat (#7453)by Nicolas Dorier · 64af6e29 · Jul 14, 2026 · 15 filesMessage 65 · AdequateInformational 20Details
Commit message · Nicolas Dorier

Add SearchFiltersPMO to avoid repeat (#7453)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode✓ 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 20/100

This commit is mostly a code cleanup and test-helper refactor. It introduces a shared test helper for search filters, switches many HTML IDs to CSS classes for easier testing, fixes a duplicate date-range filter bug, and changes a Telegram footer link from t.me to telegram.me. There is no clear security vulnerability in the diff, and the changes appear to be routine maintenance.

AI review queuedFix buildby Nicolas Dorier · 660aabdd · Jul 13, 2026 · 2 filesMessage 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 YAML syntax error in two test docker-compose files. Trailing commas after environment variable values were removed in one file, and a missing environment variable was added in the other. This is purely a build/test configuration fix with no security relevance.