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
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
AI review queuedRename attributeby Nicolas Dorier · 5854d8a3 · Nov 20, 2026 · 11 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Rename attribute
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 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.
Lower-priorityFix sorting, State badges, links and chart colors on the reports page (#7832)by Dan Ostermayer · efe6cb4b · Nov 19, 2026 · 3 filesMessage 93 · StrongTriage 0Details
Commit message · Dan Ostermayer
Fix sorting, State badges, links and chart colors on the reports page (#7832)
* Fix sorting, State badges and links for metadata fields in reports
Report fields include invoice metadata keys and values, and the person who creates an invoice sets its metadata. A field named __ob__ couldn't be sorted, because Vue adds an __ob__ key to the object that held the sort state of each field. The sort state is now kept under a prefixed field name. A value in the State column was added to its badge as a CSS class, so the text could add any class. Now only invoice and payout states add a badge class, and other values show as a plain badge. A field whose name ends in url linked any text that starts with http. Now only values that parse as http or https URLs, in any case, become links.
* Show negative BalanceChange totals in red in report charts
The chart cells checked the sign of value.d instead of value.v. For an amount, d is the number of decimals, so negative BalanceChange totals showed in green like positive ones.
* Exclude Vue href bindings from the dead-link checker
---------
Co-authored-by: ostermayer <ostermayer@users.noreply.github.com> Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Lower-priorityUpdate QRCoder to 1.9.0 (#7833)by Nicolas Dorier · 80bf163f · Nov 19, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
AI review queuedUse server translations on the invoice checkout page (#7828)by Chukwuleta Tobechi · bb14f177 · Nov 19, 2026 · 90 filesMessage 58 · ThinInformational 19Details
Commit message · Chukwuleta Tobechi
Use server translations on the invoice checkout page (#7828)
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
second-pass: unusually broad change
AI analysis · Informational 19/100
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 settings. The visible checkout text is rendered by the server. The change removes the old language selector from the checkout page and deletes many per-language checkout JSON files. It is primarily a feature/refactoring change, not a security fix.
AI review queuedUpdate dependency and .NET 10 servicing images (#7831)by Nicolas Dorier · d5ecad56 · Nov 19, 2026 · 3 filesMessage 73 · AdequateInformational 12Details
Commit message · Nicolas Dorier
Update dependency and .NET 10 servicing images (#7831)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 12/100
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 a security issue, and the diff itself does not show any code changes that would directly introduce or fix a vulnerability. It is best treated as a normal dependency refresh.
Lower-priorityUpdate Microsoft.Playwright to 1.65.1 (#7830)by Nicolas Dorier · 1ef44ea3 · Nov 18, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Security candidateHarden account and payment handlingby Andrew Camilleri (Kukks) · 20ae3337 · Nov 18, 2026 · 55 filesMessage 45 · ThinHigh 78Details
Commit message · Andrew Camilleri (Kukks)
Harden account and payment handling
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathauthentication path
AI analysis · High 78/100
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 admin rights or account status changes; stopping users from creating multiple simultaneous refunds for the same invoice; requiring extra permission when a payout approval specifies a custom exchange rate; preventing hot-wallet flags from being silently carried over to a different wallet; adding rate limits to anonymous monetization signups and LNURL invoice generation; fixing PayJoin transaction locking so funds are not accidentally double-spent; and making plugin dependency downloads safer against cycles and partial installs. The commit message and code comments frame these as hardening measures rather than a single critical vulnerability.
Lower-priorityMake public invoice and receipt link expiration configurable per store (#7818)by Nicolas Dorier · 0c3fec0c · Nov 18, 2026 · 15 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Make public invoice and receipt link expiration configurable per store (#7818)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityHide native clear button in global search input (#7827)by Carlos Marques · dfc04ca9 · Nov 18, 2026 · 2 filesMessage 81 · StrongTriage 8Details
Commit message · Carlos Marques
Hide native clear button in global search input (#7827)
* Hide native clear button in global search input
* Invalidate pending searches when restoring initial suggestions
---------
Co-authored-by: Nicolas Dorier <nicolas.dorier@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
defensive validation
Lower-priorityEscape formulas in report CSV exports (#7819)by Dan Ostermayer · 3a7aa3d3 · Nov 18, 2026 · 1 fileMessage 76 · AdequateTriage 0Details
Commit message · Dan Ostermayer
Escape formulas in report CSV exports (#7819)
Report cells that start like a spreadsheet formula now get a leading quote, the same way the wallet CSV export escapes comments and labels. Numbers, such as negative amounts, stay unchanged.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityFix the reports page for non-text values in url and State columns (#7826)by Dan Ostermayer · b32e9ae0 · Nov 17, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · Dan Ostermayer
Fix the reports page for non-text values in url and State columns (#7826)
Report fields include invoice metadata keys. The report table called string methods on any truthy value in a field whose name ends in url, and on any value in a field named State. So a value like 1 in such a url field, or a row without a State value, threw while rendering, and the whole report showed nothing. These cells now show a link or a badge only when they hold text.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityFix the reports page for field names like hasOwnProperty (#7824)by Dan Ostermayer · b4f19fab · Nov 17, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · Dan Ostermayer
Fix the reports page for field names like hasOwnProperty (#7824)
Report fields include invoice metadata keys, and the page kept the sort state of each field in a plain object keyed by field name. A field named hasOwnProperty stopped the page from loading, and a field named __proto__ couldn't be sorted. The sort state now lives in an object without a prototype.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedTranslate remaining public pages and remove invoice checkout language option (#7815)by Chukwuleta Tobechi · 1ab0a206 · Nov 17, 2026 · 19 filesMessage 58 · ThinInformational 19Details
Commit message · Chukwuleta Tobechi
Translate remaining public pages and remove invoice checkout language option (#7815)
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 19/100
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 being patched.
Lower-priorityUse planCheckoutId consistently for subscription checkout identifiers (#7817)by Nicolas Dorier · eb546253 · Nov 17, 2026 · 13 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Use planCheckoutId consistently for subscription checkout identifiers (#7817)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityMerge pull request #7816 from NicolasDorier/unnest-form-ui-routesby Nicolas Dorier · 6e4e22ef · Nov 17, 2026 · 6 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7816 from NicolasDorier/unnest-form-ui-routes
Unnest form management UI routes
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
merge-commit duplicate discount
Lower-priorityUnnest form management UI routesby Nicolas Dorier · 5b52c0c5 · Nov 17, 2026 · 6 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Unnest form management UI routes
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateMerge pull request #7780 from tumutech/fix-inventory-countsby Nicolas Dorier · 0ba97eac · Nov 17, 2026 · 11 filesMessage 73 · AdequateLow 47Details
Commit message · Nicolas Dorier
Merge pull request #7780 from tumutech/fix-inventory-counts
Fix Point of Sale and Crowdfund Perks inventory counts after unpaid invoices
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 pathauthentication pathmerge-commit duplicate discount
AI analysis · Low 47/100
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 look like more items were available than actually were. The fix tracks the invoice's previous status so inventory is only adjusted once. The commit also adds a way for tests to wait until background event processing is finished.
Security candidateFix duplicate inventory returns when expired invoices are marked invalidby tumutech · 6d4beac4 · Nov 17, 2026 · 11 filesMessage 83 · StrongLow 44Details
Commit message · tumutech
Fix duplicate inventory returns when expired invoices are marked invalid
Track previous invoice status consistently for transition events and verify inventory updates using cancellable event queue barriers.
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
boot or update pathauthentication path
AI analysis · Low 44/100
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 inventory restock if the invoice was already expired. It also adds a test-only helper to wait for background event processing. The bug is a logic error, not an externally exploitable vulnerability, but it could let a merchant or customer manipulate inventory counts in point-of-sale apps.
Lower-priorityFix Use current URL button clearing server base URLby Nicolas Dorier · bc9f9303 · Nov 17, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier
Fix Use current URL button clearing server base URL
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityApply the store language to public pages (#7675)by Chukwuleta Tobechi · f2c70fa1 · Nov 16, 2026 · 11 filesMessage 53 · ThinTriage 0Details
Commit message · Chukwuleta Tobechi
Apply the store language to public pages (#7675)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityPrune redundant test coverageby Nicolas Dorier · f41bf3e3 · Nov 16, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Prune redundant test coverage
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Mentions testing or verification! No meaningful explanatory body
AI review queuedApply store’s language on customer-facing pages (#7656)by Chukwuleta Tobechi · 55d71e89 · Nov 16, 2026 · 22 filesMessage 58 · ThinInformational 24Details
Commit message · Chukwuleta Tobechi
Apply store’s language on customer-facing pages (#7656)
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
second-pass: unusually broad change
AI analysis · Informational 24/100
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 direct evidence in the commit that this fixes an active security vulnerability; it reads as a feature or hardening change to make customer-facing language selection consistent and to prevent a SignalR hub from bypassing the store-language logic.
Lower-priorityMerge pull request #7778 from Psycarlo/fix/explain-unified-qr-modeby Nicolas Dorier · 90c21726 · Nov 16, 2026 · 5 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7778 from Psycarlo/fix/explain-unified-qr-mode
fix: explain unified QR mode in store settings
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference