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.
Lower-priorityMerge pull request #7800 from blurman-ai/fix/mark-invoice-resultby Nicolas Dorier · 27500109 · Nov 16, 2026 · 5 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7800 from blurman-ai/fix/mark-invoice-result
Report failed invoice status changes instead of showing success
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
merge-commit duplicate discount
Lower-priorityMerge pull request #7809 from efeesrefinal/fix/unexpire-extended-payment-requestby Nicolas Dorier · 4eb09122 · Nov 16, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7809 from efeesrefinal/fix/unexpire-extended-payment-request
Fix: An expired payment request stays expired after its expiry is moved to the future
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
merge-commit duplicate discount
AI review queuedMerge pull request #7810 from efeesrefinal/fix/wallet-transaction-filtersby Nicolas Dorier · 867209d1 · Nov 16, 2026 · 3 filesMessage 73 · AdequateLow 29Details
Commit message · Nicolas Dorier
Merge pull request #7810 from efeesrefinal/fix/wallet-transaction-filters
Fix: Wallet transactions listed twice when filtering by status and label
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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 29/100
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 logic added the transaction once for matching the label and again for matching the status. Second, two API endpoints that look up a single transaction by ID would crash if given an invalid transaction ID instead of returning a proper 'not found' error. The patch corrects the filtering logic and safely handles malformed transaction IDs.
Lower-priorityMerge pull request #7813 from NicolasDorier/nuget/roslyn-5.12.0-20261116by Nicolas Dorier · c8fec826 · Nov 16, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7813 from NicolasDorier/nuget/roslyn-5.12.0-20261116
Update Microsoft.CodeAnalysis.CSharp to 5.12.0
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
merge-commit duplicate discount
Lower-priorityUpdate Microsoft.CodeAnalysis.CSharp to 5.12.0by AlfredTheBot69 · b41537c4 · Nov 16, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · AlfredTheBot69
Update Microsoft.CodeAnalysis.CSharp to 5.12.0
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge pull request #7811 from AlfredTheBot69/alfred/nuget-nbitcoin-10.0.21by Nicolas Dorier · a20e06b3 · Nov 14, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7811 from AlfredTheBot69/alfred/nuget-nbitcoin-10.0.21
Update NBitcoin to 10.0.21
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-priorityUpdate NBitcoin to 10.0.21by AlfredTheBot69 · 574b0c6a · Nov 13, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · AlfredTheBot69
Update NBitcoin to 10.0.21
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge pull request #7807 from btcpayserver/feat/lnd-v0.21.8-betaby Roxanne · 95218020 · Nov 12, 2026 · 4 filesMessage 58 · ThinTriage 0Details
Commit message · Roxanne
Merge pull request #7807 from btcpayserver/feat/lnd-v0.21.8-beta
Bump LND to v0.21.8-beta
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
AI review queuedBump LND to v0.21.8-betaby r1ckstardev · 4bcdc689 · Nov 12, 2026 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · r1ckstardev
Bump LND to v0.21.8-beta
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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 behavior of BTCPay Server itself. There is no evidence in the commit or supplied references that this is a security fix or introduces a vulnerability.
Lower-priorityMerge pull request #7806 from NicolasDorier/fix/notification-filter-pagingby Nicolas Dorier · a33c257d · Nov 12, 2026 · 5 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7806 from NicolasDorier/fix/notification-filter-paging
Fix notification filtering and schedule retention cleanup
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
merge-commit duplicate discount
Lower-priorityMerge pull request #7805 from AlfredTheBot69/alfred/nuget-2026-11-12by Nicolas Dorier · 7fd4c708 · Nov 12, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7805 from AlfredTheBot69/alfred/nuget-2026-11-12
Update NuGet dependencies
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-priorityFix notification filtering and schedule retention cleanupby Nicolas Dorier · 0a54850e · Nov 12, 2026 · 5 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier
Fix notification filtering and schedule retention cleanup
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge pull request #7796 from efeesrefinal/fix/notification-pagingby Nicolas Dorier · 38c8b9e7 · Nov 12, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7796 from efeesrefinal/fix/notification-paging
Fix notification paging ignoring skip, and return 404 for an unknown notification
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
merge-commit duplicate discount
AI review queuedUpdate NuGet dependenciesby AlfredTheBot69 · 9951be68 · Nov 11, 2026 · 2 filesMessage 35 · OpaqueInformational 11Details
Commit message · AlfredTheBot69
Update NuGet dependencies
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 11/100
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 references were provided. It looks like a routine dependency maintenance change.
Lower-priorityBump LND test images to v0.21.7-beta and handle Ubuntu DNS outages (#7803)by Roxanne · d6b31016 · Nov 11, 2026 · 5 filesMessage 68 · AdequateTriage 0Details
Commit message · Roxanne
Bump LND test images to v0.21.7-beta and handle Ubuntu DNS outages (#7803)
68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityvalidate plan grace, trial and reminder days (#7802)by Chukwuleta Tobechi · 90e87ef2 · Nov 11, 2026 · 5 filesMessage 58 · ThinTriage 8Details
Commit message · Chukwuleta Tobechi
validate plan grace, trial and reminder days (#7802)
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
defensive validation
AI review queuedUpdate NuGet dependencies and compatibilityby Alfred · bef0935c · Nov 11, 2026 · 11 filesMessage 45 · ThinLow 34Details
Commit message · Alfred
Update NuGet dependencies and compatibility
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 · Low 34/100
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 wallet transaction CSV export. The new code deliberately prefixes spreadsheet formula characters (like =, +, @) with an apostrophe so that exported CSV files are less likely to trigger malicious formula injection when opened in Excel or similar programs. The commit does not say it is fixing a security bug, and no external advisory is supplied.
Lower-priorityMerge pull request #7797 from AlfredTheBot69/nuget/githubactionsreport-2.5.2by Nicolas Dorier · 2cbc3d87 · Nov 11, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7797 from AlfredTheBot69/nuget/githubactionsreport-2.5.2
Bump Microsoft.Testing.Extensions.GitHubActionsReport to 2.5.2
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityBump Microsoft.Testing.Extensions.GitHubActionsReport to 2.5.2by AlfredTheBot69 · 3ebc4547 · Nov 11, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · AlfredTheBot69
Bump Microsoft.Testing.Extensions.GitHubActionsReport to 2.5.2
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Security candidateMerge pull request #7795 from tumutech/fix-api-key-permission-usage-analysisby Nicolas Dorier · c9a45b12 · Nov 11, 2026 · 4 filesMessage 73 · AdequateInformational 24Details
Commit message · Nicolas Dorier
Merge pull request #7795 from tumutech/fix-api-key-permission-usage-analysis
Fix API key View Usage crash with multi-store permission usage
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
credential or privilege statemerge-commit duplicate discount
AI analysis · Informational 24/100
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 displayed so store-specific permissions are counted separately instead of being lumped together. It is primarily a reliability/functional bug fix; there is no direct evidence it created or fixed a security vulnerability that an attacker could exploit.
Security candidateFix API key View Usage crash with multi-store permission usageby tumutech · 0ade56df · Nov 10, 2026 · 4 filesMessage 50 · ThinInformational 22Details
Commit message · tumutech
Fix API key View Usage crash with multi-store permission usage
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Informational 22/100
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 are stored and displayed so that store-specific permissions are counted separately instead of being lumped together or duplicated. There is no direct evidence this was a security vulnerability, but the bug could have caused misleading usage statistics for API keys.
Lower-priorityUpdate LND image to v0.21.6-beta-1 (#7790)by Nicolas Dorier · c16fc29e · Nov 5, 2026 · 4 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Update LND image to v0.21.6-beta-1 (#7790)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityAdd per-user language preferences (#7616)by Chukwuleta Tobechi · 9878023b · Nov 5, 2026 · 14 filesMessage 53 · ThinTriage 0Details
Commit message · Chukwuleta Tobechi
Add per-user language preferences (#7616)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedFix RoundToSignificant for negative amounts (#7782)by Amartya Vikram Singh · 6899974a · Nov 5, 2026 · 3 filesMessage 81 · StrongModerate 51Details
Commit message · Amartya Vikram Singh
Fix RoundToSignificant for negative amounts (#7782)
The relative error was divided by the signed value, so for a negative amount it was never positive and the first rounding was always accepted. Small negative amounts were rounded to zero (-0.0004 with divisibility 2 became -0.00) instead of keeping their significant digits like positive ones (0.0004 stays 0.0004).
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: security-sensitive path
AI analysis · Moderate 51/100
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 positive ones. Tiny negative amounts could be rounded to zero (for example, -0.0004 became -0.00) while the equivalent positive amount kept its precision. The same patch also makes sure transaction fee bumps are never rounded down below the Bitcoin network's minimum relay-fee increase, preventing a fee-bump transaction from being rejected for paying too little.
Lower-priorityBump Core Lightning test images to v26.06.10 (#7789)by Roxanne · 4a7f1f08 · Nov 4, 2026 · 4 filesMessage 83 · StrongTriage 0Details
Commit message · Roxanne
Bump Core Lightning test images to v26.06.10 (#7789)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference