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 #7695 from btcpayserver/fix/frontend-url-notificationsby Nicolas Dorier · 0fcb9c46 · Oct 20, 2026 · 4 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7695 from btcpayserver/fix/frontend-url-notifications
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-priorityMerge pull request #7700 from btcpayserver/fix/subscription-backend-hardeningby Nicolas Dorier · ec008753 · Oct 20, 2026 · 5 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7700 from btcpayserver/fix/subscription-backend-hardening
Harden subscription checkout and inputs
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-priorityHarden subscription checkout and inputsby Nicolas Dorier · 213c514e · Oct 20, 2026 · 5 filesMessage 45 · ThinTriage 8Details
Commit message · Nicolas Dorier
Harden subscription checkout and inputs
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validation
Lower-priorityMerge pull request #7703 from NicolasDorier/fix/7702-lnurl-payout-roundingby Nicolas Dorier · 7a436b52 · Oct 20, 2026 · 4 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7703 from NicolasDorier/fix/7702-lnurl-payout-rounding
Round LNURL payouts to whole satoshis
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-priorityRound LNURL payouts to whole satoshisby Nicolas Dorier · 68838c6c · Oct 20, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Round LNURL payouts to whole satoshis
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge pull request #7682 from btcpayserver/bump-bitcoin-32.0rc4by Nicolas Dorier · ae862810 · Oct 20, 2026 · 8 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7682 from btcpayserver/bump-bitcoin-32.0rc4
Prefer Bitcoin Core fee estimates
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-priorityPrefer Bitcoin Core fee estimatesby Nicolas Dorier · 19ad166a · Oct 20, 2026 · 8 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Prefer Bitcoin Core fee estimates
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateHarden wallet error handling and PSBT input (#7701)by Andrew Camilleri · 717ff11d · Oct 20, 2026 · 3 filesMessage 58 · ThinModerate 51Details
Commit message · Andrew Camilleri
Harden wallet error handling and PSBT input (#7701)
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 boundarydefensive validationsigning or wallet path
AI analysis · Moderate 51/100
This commit tightens up how BTCPay Server handles user-supplied PSBT (Bitcoin transaction) data. It adds a size limit check for PSBTs pasted as text (previously only file uploads were checked) and stops including the raw error message from a failed payjoin receiver in the user-facing error. These changes reduce the risk of oversized input causing resource problems and prevent a malicious or misbehaving payjoin receiver from injecting text into the server's error pages.
AI review queuedBound profile and wallet object fields (#7693)by Andrew Camilleri · 4fa9a330 · Oct 19, 2026 · 3 filesMessage 68 · AdequateLow 44Details
Commit message · Andrew Camilleri
Bound profile and wallet object fields (#7693)
* Bound profile and wallet object fields
* Close profile and wallet validation gaps
68/100 · AdequateMessage clarity
✓ 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 pathsecond-pass: security-sensitive path
AI analysis · Low 44/100
This commit adds input-length and type checks for user profile fields (name and avatar URL) and for transaction comments on wallet objects. Before the change, an attacker could supply oversized names or image URLs, or store very large or wrongly-typed transaction comments, through the Greenfield API. The patch rejects values that exceed set limits and ensures transaction comments are strings, which reduces the risk of database bloat, denial-of-service, and unexpected behavior when the data is later displayed.
Lower-priorityBound Lightning invoice inputs (#7692)by Andrew Camilleri · a8546515 · Oct 19, 2026 · 3 filesMessage 76 · AdequateTriage 0Details
Commit message · Andrew Camilleri
Bound Lightning invoice inputs (#7692)
* Bound lightning invoice inputs
* Measure Lightning metadata by serialized bytes
* Match persisted Lightning metadata format
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityHarden webhook storage and delivery (#7694)by Andrew Camilleri · f4cb337f · Oct 19, 2026 · 8 filesMessage 53 · ThinTriage 8Details
Commit message · Andrew Camilleri
Harden webhook storage and delivery (#7694)
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
defensive validation
Lower-priorityDirect security reports to GitHub Security Advisories (#7683)by Andrew Camilleri · c7ed9579 · Oct 19, 2026 · 1 fileMessage 63 · AdequateTriage 0Details
Commit message · Andrew Camilleri
Direct security reports to GitHub Security Advisories (#7683)
63/100 · AdequateMessage clarity
✓ Specific, 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
documentation-only discount
Lower-priorityHarden subscription inputs and credit (#7689)by Andrew Camilleri · bdee408d · Oct 19, 2026 · 4 filesMessage 53 · ThinTriage 8Details
Commit message · Andrew Camilleri
Harden subscription inputs and credit (#7689)
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
defensive validation
Security candidateEnforce API key permission scope (#7684)by Andrew Camilleri · 1348bd05 · Oct 19, 2026 · 3 filesMessage 53 · ThinHigh 77Details
Commit message · Andrew Camilleri
Enforce API key permission scope (#7684)
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
credential or privilege stateauthentication path
AI analysis · High 77/100
This commit fixes a permission-handling bug in BTCPay Server's Greenfield API. Previously, an API key that was only supposed to manage a single store could be used to create or request broader, server-wide permissions it did not actually have. The change now checks every requested permission against what the current key is allowed to grant, and it also tightens how store-scoped permissions are matched during authorization. In short, it stops a limited key from being upgraded into a more powerful one.
Lower-priorityUpdate vulnerable framework packages (#7685)by Andrew Camilleri · 4142b3a1 · Oct 19, 2026 · 6 filesMessage 58 · ThinTriage 0Details
Commit message · Andrew Camilleri
Update vulnerable framework packages (#7685)
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
Lower-priorityFix store invitation expiry text (#7691)by Nicolas Dorier · a961b748 · Oct 19, 2026 · 2 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Fix store invitation expiry text (#7691)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityHarden rate rules and invoice arithmetic (#7686)by Andrew Camilleri · ad47c0f3 · Oct 19, 2026 · 5 filesMessage 53 · ThinTriage 8Details
Commit message · Andrew Camilleri
Harden rate rules and invoice arithmetic (#7686)
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
defensive validation
Lower-priorityBound persisted store URLs (#7688)by Andrew Camilleri · 4c28a075 · Oct 19, 2026 · 2 filesMessage 53 · ThinTriage 0Details
Commit message · Andrew Camilleri
Bound persisted store URLs (#7688)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityHarden rate provider responses (#7687)by Andrew Camilleri · 3a742001 · Oct 19, 2026 · 6 filesMessage 53 · ThinTriage 8Details
Commit message · Andrew Camilleri
Harden rate provider responses (#7687)
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
defensive validation
Lower-priorityKeep Lightning payouts in progress when a payment lookup returns no result (#7679)by Shin · 39be587e · Oct 19, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Shin
Keep Lightning payouts in progress when a payment lookup returns no result (#7679)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Security candidateFix LNURL URI QR code casingby Nicolas Dorier · c5041bdb · Oct 19, 2026 · 5 filesMessage 45 · ThinLow 25Details
Commit message · Nicolas Dorier
Fix LNURL URI QR code casing
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 25/100
This commit fixes how QR codes are generated for LNURL (a way to pay or log in via Bitcoin Lightning). Previously, non-Bech32 URI-style LNURLs were being converted to ALL UPPERCASE for QR codes, which can break some QR readers and wallet apps because the 'lightning:' prefix should stay lowercase. The change makes QR codes keep the correct casing depending on the LNURL format, reducing the chance that a customer or user can't scan or pay.
Lower-priorityfix: show payment method names instead of IDs in checkout settings (#7676)by Carlos Marques · 70c07d3b · Oct 17, 2026 · 2 filesMessage 70 · AdequateTriage 0Details
Commit message · Carlos Marques
fix: show payment method names instead of IDs in checkout settings (#7676)
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
Lower-priorityHide copy button for empty transaction ids in reports (#7677)by Carlos Marques · 79524c7d · Oct 17, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Carlos Marques
Hide copy button for empty transaction ids in reports (#7677)
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-priorityBump Tor test image to 0.4.9.14by Nicolas Dorier · ccb1633e · Oct 16, 2026 · 4 filesMessage 55 · ThinTriage 0Details
Commit message · Nicolas Dorier
Bump Tor test image to 0.4.9.14
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body