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.
Security candidateRefactor: Move translations classes in its own pluginby Nicolas Dorier · 64d5a893 · Feb 20, 2026 · 26 filesMessage 62 · AdequateInformational 15Details
Commit message · Nicolas Dorier
Refactor: Move translations classes in its own plugin
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
boot or update path
AI analysis · Informational 15/100
This commit is a routine code reorganization: it moves BTCPay Server's translation/localization code from the core server project into a dedicated 'Translations' plugin. The same dictionary-management features, language-pack download, and localization services are preserved, just relocated. There is no indication of a security fix or vulnerability being addressed.
Security candidateFix: Can't upgrade/downgrade a Lifetime subscription (#7194)by Nicolas Dorier · 41295c17 · Feb 19, 2026 · 2 filesMessage 70 · AdequateInformational 20Details
Commit message · Nicolas Dorier
Fix: Can't upgrade/downgrade a Lifetime subscription (#7194)
Fix #7193
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
update trust
AI analysis · Informational 20/100
This commit fixes a JavaScript crash in the subscription portal. When a user had a lifetime subscription, the page did not show an auto-renewal checkbox, but the script still tried to attach an event listener to it. That caused a browser error that blocked the rest of the page's JavaScript, making it impossible to upgrade or downgrade the subscription. The fix simply checks whether the checkbox exists before attaching the listener. There is no direct security vulnerability here; it is a functional bug with a minor denial-of-service-like effect on the UI.
AI review queuedAdd test logby Nicolas Dorier · 5ee050b1 · Feb 18, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Add test log
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 a test file. It adds one extra assertion and reorders two existing assertions. There is no change to production code, no security fix, and no vulnerability.
AI review queuedpre bump versionby Nicolas Dorier · 1164dfa7 · Feb 18, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
pre bump version
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 a single version number in a build file from 2.3.5 to 2.3.6. There is no code change, no bug fix, and no security-related content.
AI review queuedRemove garbage from csprojby Nicolas Dorier · 2b87402a · Feb 18, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Remove garbage from csproj
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 cleans up leftover build configuration entries in two C# project files. It removes duplicate or stale entries that told the build system how to treat certain view files and folders. There is no indication this change fixes or introduces a security problem; it appears to be routine housekeeping.
AI review queuedRemove runtime compilationby Nicolas Dorier · fb491d51 · Feb 18, 2026 · 4 filesMessage 35 · OpaqueLow 26Details
Commit message · Nicolas Dorier
Remove runtime compilation
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 26/100
This commit removes a feature called 'Razor runtime compilation' from the main BTCPay Server application. Previously, in debug/development builds, the server could recompile web page templates (Razor views) on the fly while running. The change makes the server always use pre-compiled views instead. Runtime compilation is useful for developers but can increase attack surface, so removing it from production-like builds is a hardening move. A special test-only flag is added so developers can still enable it for testing.
AI review queuedBump libraries and move to net10by Nicolas Dorier · 54336889 · Feb 18, 2026 · 23 filesMessage 45 · ThinInformational 19Details
Commit message · Nicolas Dorier
Bump libraries and move to net10
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 19/100
This commit upgrades BTCPay Server from .NET 8 to .NET 10 and bumps many third-party libraries. It also makes small code changes to adapt to new framework APIs. The update itself is a routine maintenance change, but it removes some older dependencies and includes a few minor hardening tweaks, such as adding a null check before processing payment requests and filtering swagger files by extension. There is no direct evidence in the commit that this fixes a known security vulnerability, and the commit message does not mention security.
AI review queuedUpdate wallet folder access instructions for Wasabi (#7192)by nopara73 · e7e2bc96 · Feb 17, 2026 · 1 fileMessage 58 · ThinInformational 15Details
Commit message · nopara73
Update wallet folder access instructions for Wasabi (#7192)
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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit changes a single line of on-screen help text in BTCPay Server. It updates the instructions for Wasabi wallet users, telling them to search for 'wallet folder' instead of using an older menu path. There is no code behavior change, no security fix, and no vulnerability.
AI review queuedFix pre release utilityby Nicolas Dorier · a13603a8 · Feb 17, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix pre release utility
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 updates a single test file so that a language-pack test reads the list of downloadable languages from a shared service class instead of parsing a Razor view file directly. It is a test maintenance/refactoring change with no visible security relevance.
AI review queuedFix flaky testby Nicolas Dorier · 5a27b3f7 · Feb 17, 2026 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix flaky test
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 fixes a flaky automated UI test by making the test wait until a notifications component has finished rendering before checking its contents. The code change adds a 'rendered' CSS class once Blazor has finished pre-rendering and updates the test to look for that class. There is no security relevance.
AI review queuedBump btcpayby Nicolas Dorier · 05c79c1c · Feb 17, 2026 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Bump btcpay
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 is a routine version bump from 2.3.4 to 2.3.5 and updates the changelog. It does not change any application code, configuration, or security settings. There is nothing in the diff that introduces, fixes, or alters a security-relevant behavior.
AI review queuedMinor refactoringby Nicolas Dorier · cf30de00 · Feb 16, 2026 · 2 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Minor refactoring
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a small code cleanup in BTCPay Server's admin translation pages. It changes how a helper service is passed into the controller, switching from method-level injection to constructor-level injection. There is no visible change in behavior, no new security feature, and no bug fix apparent from the diff.
Merge pull request #7185 from Abhijay007/feat/updateTranslations
feat: added ability to update translations
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Low 29/100
This commit adds a feature that lets BTCPay Server administrators download and update language translation packs from a GitHub repository. The code fetches JSON translation files over the internet, stores them in the server's database, and tracks whether a newer version is available. There is no clear security bug in the diff, but the design introduces a supply-chain and server-side request risk that should be reviewed carefully.
* Use overflow-wrap instead of deprecated word-break for checkout text
* Add client-side maxlength to checkout text textarea
81/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Low 32/100
This commit adds a new store setting that lets merchants type a short custom message shown on the checkout page. The text is limited to 500 characters, stored as plain text, and displayed using a safe Vue.js directive that escapes HTML. There is no obvious security bug in the change itself, but it is a new user-controlled text field rendered on a payment page, so it needs careful handling to avoid future misuse (for example, if someone later changes how the text is displayed).
AI review queuedAllow BTCPay Server to start without any on-chain payment methodby Nicolas Dorier · ab0a4910 · Feb 15, 2026 · 25 filesMessage 81 · StrongLow 28Details
Commit message · Nicolas Dorier
Allow BTCPay Server to start without any on-chain payment method
The default value of `--chains` (or `BTC_CHAINS`) is `BTC`, so it wasn't possible to start BTCPay Server without at least BTC (or other Bitcoin fork) support.
This PR add a new configuration `--nodefaultchain` (or `BTCPAY_NODEFAULTCHAIN`). When specified, an empty `--chains` will start BTCPay Server without any Bitcoin like chain support.
Partially fix #7175.
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 28/100
This commit lets BTCPay Server start without any Bitcoin-like blockchain payment method enabled. It adds a new --nodefaultchain option and updates many parts of the code so the app no longer assumes Bitcoin is always available. Most changes are defensive null checks and UI message adjustments, but the broad scope means there is a risk of missed edge cases where the code still expects a default network and could crash or behave unexpectedly.
Security candidatePass userHandle to FIDO authby Nicolas Dorier · 69c99a1c · Feb 12, 2026 · 1 fileMessage 50 · ThinLow 33Details
Commit message · Nicolas Dorier
Pass userHandle to FIDO auth
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
authentication path
AI analysis · Low 33/100
This commit changes the WebAuthn/FIDO login JavaScript so that it now sends an extra piece of information, called the userHandle, to the server when a user logs in with a security key or passkey. The userHandle helps the server identify which account the credential belongs to. Without it, the server may have to guess the account from the credential ID alone, which can cause login failures or, in some FIDO implementations, allow a credential to be associated with the wrong account. The change is small and looks like a correctness fix rather than a full security patch.
Security candidateThrottle API calls with Basic auth (#7177)by Nicolas Dorier · a75b9517 · Feb 12, 2026 · 8 filesMessage 58 · ThinModerate 66Details
Commit message · Nicolas Dorier
Throttle API calls with Basic auth (#7177)
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Moderate 66/100
This change adds speed bumps (rate limiting) to API logins that use username-and-password Basic authentication. It is a hardening fix: before, attackers could make unlimited rapid login attempts through the API; now those attempts are throttled after the account is more than five minutes old. The patch also improves error messages so the server can tell callers exactly why authentication failed, including when they are rate-limited.
AI review queuedBump HtmlSanitizerby Nicolas Dorier · cb13a2a3 · Feb 11, 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
This commit simply updates a third-party HTML-cleaning library (HtmlSanitizer) from version 8.0.838 to 9.0.892 in the BTCPay Server project. The change is a one-line version bump in a project file. It is likely intended to pick up bug fixes or security fixes in the dependency, but the commit message does not say what those fixes are, and no security advisory or changelog was provided. On its own, this diff does not show any vulnerability in BTCPay Server's code, only that a dependency was refreshed.
AI review queuedfeat(dashboard): support multi-crypto wallet balance widgets (#7110)by Sup3rlativ3 · 94a34596 · Feb 10, 2026 · 6 filesMessage 93 · StrongInformational 15Details
Commit message · Sup3rlativ3
feat(dashboard): support multi-crypto wallet balance widgets (#7110)
* feat(dashboard): support multi-crypto wallet balance widgets
* fix: keep store numbers aligned with setup guide
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine feature update for the BTCPay Server dashboard. It adds the ability to display wallet balance widgets for multiple cryptocurrencies at once, fixes a potential crash when looking up a cryptocurrency handler, and adjusts the dashboard layout. There is no indication of a security fix or vulnerability being addressed.
Security candidateRefactor : Added missing translations strings for various files (#6897)by Abhijay Jain · bcdd6dc8 · Feb 9, 2026 · 26 filesMessage 81 · StrongInformational 15Details
Commit message · Abhijay Jain
Refactor : Added missing translations strings for various files (#6897)
* refactor : Added missing translation strings to Wallet Management
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* refactor : Added missing translation strings to Store Management
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* Refactor : Added missing translation strings to Server Administration
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* Refactor : Added missing translation strings to User Account
* Refactor : Added missing translation strings Invoice and Payment
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* Refactor : Added missing translation strings other files
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* Refactor : Added missing translation strings other missed files
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* refactor: fixed some problematic strings
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* Refactor: removed dynamic strings
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* refactor: addressed requested changes
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* refactor : removed public facing page
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* refactor: updated branch and addressed coderabit comments
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* Update default translations and resolve merge conflicts
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
* refactor: removed duplicate attributes
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
---------
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
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
seed or entropy pathsigning or wallet pathboot or update path
AI analysis · Informational 15/100
This commit is a routine internationalization (i18n) refactor. It marks more user-interface text strings in BTCPay Server's web pages as translatable and updates the default translation dictionary. There is no security-relevant change to application logic, access control, cryptography, or data handling.
AI review queuedAdd nicolasdorier.asc file to check signed commitby Nicolas Dorier · 1ed22df3 · Jan 28, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Nicolas Dorier
Add nicolasdorier.asc file to check signed commit
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 adds a public PGP key file and updates a CI script to import it when verifying that commits are cryptographically signed. It is a hardening/operational improvement to the project's build verification process, not a fix for a software vulnerability in BTCPay Server itself.
AI review queuedClarify example of placeholder in the email rule pageby Nicolas Dorier · 49801ccd · Jan 28, 2026 · 1 fileMessage 30 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Clarify example of placeholder in the email rule page
30/100 · OpaqueMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only updates a user-facing help message in the email rules page. It adds a second example placeholder ({Subscriber.Metadata.accessKey}) alongside the existing one ({Invoice.Metadata.itemCode}) to make the documentation clearer. There is no code behavior change and no security relevance.
AI review queuedSmall cleanupsby Nicolas Dorier · 622c438a · Jan 28, 2026 · 2 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Small cleanups
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine cleanup. It removes two unused namespace imports from a webhook trigger provider file and adds null checks and a page-load wait to automated UI tests. There is no change to production logic, no security fix, and no disclosed vulnerability.
AI review queuedTests: Flakyby Nicolas Dorier · f8d145a4 · Jan 28, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Tests: Flaky
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 changes two lines in a single test file to make a flaky test more reliable. It replaces a broad check that the page contains the text 'Pay123' with a more precise check that a specific element with the expected ID shows the text 'Pay123'. This is a test-quality improvement, not a security fix.
AI review queuedAdd Subscriber.Metadata as email placeholder, fix Offering.Metadata and Customer.Metadata placeholderby Nicolas Dorier · ea0d4918 · Jan 28, 2026 · 3 filesMessage 30 · OpaqueInformational 19Details
Commit message · Nicolas Dorier
Add Subscriber.Metadata as email placeholder, fix Offering.Metadata and Customer.Metadata placeholder
30/100 · OpaqueMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 19/100
This commit fixes a bug in BTCPay Server's subscription email feature where metadata placeholders for offerings and customers didn't work, and adds a new placeholder for subscriber metadata. The metadata strings are now parsed as JSON objects so email templates can correctly read individual metadata fields. There is no clear security vulnerability here; it is a functional bug fix with a minor side effect that malformed metadata could now cause a parsing error when an email is generated.