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
This commit changes a single word in a build script's status message, from 'if it is possible' to 'whether it is possible'. There is no functional, security, or behavioral change to the software.
AI review queuedFix flaky testby Nicolas Dorier · 34ce3589 · Sep 3, 2026 · 1 fileMessage 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 adds one extra wait/check to an automated test that verifies email rules appear in a web page. It is purely a test-stability fix and does not change any production code, user-facing behavior, or security boundary.
AI review queuedFix github reports in CIby Nicolas Dorier · 4208bf71 · Sep 3, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix github reports in CI
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
This commit changes a CI test script so that GitHub Actions can write step summary reports to the correct file path inside a Docker container. It is a build/test infrastructure fix with no apparent security relevance.
AI review queuedValidate support URL scheme to prevent stored script injection (#7537)by Chukwuleta Tobechi · a6b81460 · Sep 2, 2026 · 3 filesMessage 85 · StrongModerate 66Details
Commit message · Chukwuleta Tobechi
Validate support URL scheme to prevent stored script injection (#7537)
* Validate support URL scheme to prevent stored script injection
* make get request readable
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
This commit fixes a stored cross-site scripting (XSS) risk in BTCPay Server's store settings. Merchants can set a 'Support URL' that is shown to customers during checkout. Before this fix, an attacker with access to store settings could enter a URL using the 'javascript:' scheme, such as 'javascript:document.body.dataset.pwned=1'. When a customer later clicked the support link, the browser would run the attacker's JavaScript in the checkout page. The patch now rejects any support URL whose scheme is not http, https, or mailto, both in the web UI and in the Greenfield API.
✓ 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 · Low 37/100
This commit adds a new 'store invitations' feature to BTCPay Server. Store owners can now invite users by email with a time-limited link instead of adding them immediately. The change introduces new database tables, API endpoints, web pages, email notifications, and security checks. It also tightens some existing rules: only server admins can skip the invitation flow, and the last store owner cannot have their role changed or be removed. The code appears to be a deliberate security-hardening feature rather than a fix for an active vulnerability, but it changes who can gain store access and how.
AI review queuedMerge branch 'remove-ssh'by Nicolas Dorier · d738def9 · Aug 30, 2026 · 48 filesMessage 35 · OpaqueLow 47Details
Commit message · Nicolas Dorier
Merge branch 'remove-ssh'
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This commit removes the built-in SSH client from BTCPay Server and replaces it with a local helper program called 'btcpay-host'. Instead of the application opening SSH connections to the server host, it now runs a configurable local executable to perform maintenance tasks such as updating, restarting, changing the domain, and managing authorized SSH keys. This is a significant architectural change that reduces the application's direct network attack surface, but it also introduces a new local command-execution path that must be trusted and properly secured.
AI review queuedAvoid unintended routeby Nicolas Dorier · e6f7b93a · Aug 28, 2026 · 1 fileMessage 28 · OpaqueLow 46Details
Commit message · Nicolas Dorier
Avoid unintended route
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 46/100
This small change marks an internal base class called VaultController with [NonController] so ASP.NET MVC does not accidentally expose it as a public web route. Without this attribute, MVC's route discovery could have treated derived vault controllers as reachable HTTP endpoints, potentially exposing internal hardware-wallet/vault operations over the web.
AI review queuedbump libsby Nicolas Dorier · bc3daaf7 · Aug 27, 2026 · 4 filesMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
bump libs
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 simply updates several third-party software libraries (dependencies) to newer patch or minor versions. There are no code changes in BTCPay Server itself, and the commit message gives no indication that any of the updates fix a security problem. Without external references linking these specific library versions to known vulnerabilities, this looks like a routine maintenance update.
AI review queuedStop wallet Label from falling back to the derivation scheme (#7521)by Chukwuleta Tobechi · 91f07db2 · Aug 27, 2026 · 1 fileMessage 58 · ThinInformational 18Details
Commit message · Chukwuleta Tobechi
Stop wallet Label from falling back to the derivation scheme (#7521)
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 18/100
This commit changes what text BTCPay Server's API returns as the 'Label' for an on-chain wallet. Previously, if no custom label was set, the API would leak the wallet's technical derivation scheme (a string describing how keys are generated) as the label. Now it returns an empty string instead. This is primarily an information-disclosure cleanup, not a direct exploit.
AI review queuedReplace CircleCI with GitHub Actions (#7520)by Nicolas Dorier · aaa168b0 · Aug 27, 2026 · 17 filesMessage 53 · ThinInformational 15Details
Commit message · Nicolas Dorier
Replace CircleCI with GitHub Actions (#7520)
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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine infrastructure change: BTCPay Server is switching its automated testing and release system from CircleCI to GitHub Actions. It copies the same test scripts, signing checks, and Docker publishing steps into GitHub Actions workflows. There is no change to the actual BTCPay Server application code that users interact with, and nothing in the commit suggests a security vulnerability was fixed or introduced.
AI review queuedPass store to payment method config validation (#7513)by Nicolas Dorier · b89aefb2 · Aug 27, 2026 · 4 filesMessage 58 · ThinLow 25Details
Commit message · Nicolas Dorier
Pass store to payment method config validation (#7513)
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 · Low 25/100
This commit changes how BTCPay Server validates payment method settings so that the store object is passed into the validation process. The change itself only adds a new piece of information (the store) to validation contexts; it does not by itself fix a visible bug or block an attack. Without the rest of the related code, it is unclear whether this prevents a security issue or is just a refactoring/cleanup step.
AI review queuedFix contradictary skill instructionby Nicolas Dorier · caf6eede · Aug 26, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix contradictary skill instruction
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This commit removes two contradictory sentences from an internal documentation file that tells contributors how to write pull request descriptions. One sentence had told them not to write about testing strategy, while another told them to add a testing note. The change only affects contributor guidance, not the BTCPay Server software that users or merchants interact with.
AI review queuedFix flaky testby Nicolas Dorier · b29aaa94 · Aug 26, 2026 · 1 fileMessage 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 is a tiny one-line change to a unit test helper that fetches cryptocurrency exchange rates from BTCTurk. It adds an extra sanity check: it ignores any exchange rate where the bid price (what buyers are offering) is higher than the ask price (what sellers are asking), because that is an impossible/inverted market state. The commit message says it is fixing a flaky test, not a security bug.
AI review queuedDo not depend on SSH for host commandsby Nicolas Dorier · 17acfe8a · Aug 25, 2026 · 46 filesMessage 45 · ThinLow 45Details
Commit message · Nicolas Dorier
Do not depend on SSH for host commands
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 · Low 45/100
This commit rewrites how BTCPay Server performs host-level maintenance. Instead of the web application opening SSH connections directly to the host, it now runs a local helper program called 'btcpay-host'. The Docker image includes a wrapper that can still forward those calls over SSH, but the core application no longer needs SSH credentials or the SSH.NET library. The change removes a large amount of SSH-related code and adds a new plugin for maintenance actions. It is primarily an architectural/security-hardening change rather than a clear-cut fix for a single vulnerability.
AI review queuedfix testby Nicolas Dorier · f78d6c20 · Aug 24, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
fix test
0/100 · OpaqueMessage clarity
✓ Mentions testing or verification! 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 is a one-line change to a test file. It updates a test case that checks for a duplicate email error so that it also provides a current password. The change does not modify any production code and has no direct security impact on the BTCPay Server application itself.
AI review queuedUpdate Changelogby Nicolas Dorier · fbf761f3 · Aug 7, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update Changelog
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit only edits the wording of a changelog entry for BTCPay Server 2.4.2. It does not change any code, configuration, or executable files. The edit makes the release sound more urgent, but the commit itself is purely documentation and contains no security fix.
AI review queuedChangelog for 2.4.2by Nicolas Dorier · 3e2928cf · Aug 7, 2026 · 2 filesMessage 38 · OpaqueModerate 64Details
Commit message · Nicolas Dorier
Changelog for 2.4.2
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 · Moderate 64/100
This commit is a version bump and changelog for BTCPay Server 2.4.2. The changelog describes two security-related changes: disabling Basic authentication by default shortly after account creation, and fixing a TOTP two-factor authentication bypass when using Greenfield Basic authentication. The actual code fixes are not shown in this commit, so we can only see the vendor's description of the issues. The vendor rates these as 'not critical' but still recommends updating.
AI review queuedUpdate translationsby Nicolas Dorier · 8d5f52da · Aug 6, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update translations
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit only adds, removes, and reorders English text strings used for translations and user-interface labels in BTCPay Server. There are no code logic changes, no security settings being enabled or disabled, and no behavior changes. It is a routine localization/string update.
AI review queuedbump depsby Nicolas Dorier · 1c16e265 · Aug 6, 2026 · 10 filesMessage 0 · OpaqueLow 25Details
Commit message · Nicolas Dorier
bump deps
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 25/100
This commit updates several third-party software libraries and a test Docker image to newer versions. It also removes one library (AngleSharp) that was no longer needed. Dependency updates can fix security bugs in those external packages, but the commit message gives no details, and the diff itself does not show any direct vulnerability or attack path in BTCPay Server's own code.
AI review queuedContainerize store settings views into sections & clean up views (#7448)by dstrukt · b8774051 · Aug 4, 2026 · 20 filesMessage 58 · ThinInformational 15Details
Commit message · dstrukt
Containerize store settings views into sections & clean up views (#7448)
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 15/100
This commit is a user-interface redesign, not a security fix. It wraps store settings pages in new visual 'section' containers, updates headings and spacing, and adjusts CSS styling. No code behavior, permissions, or data handling changed.
✓ 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 23/100
This commit adds a user-facing preference feature to BTCPay Server's wallet transactions table: a dropdown that lets users show, hide, and reorder columns. Preferences are saved in the browser's localStorage. The change is a routine UI enhancement and does not appear to be a security fix. There is no indication from the commit that the vendor considers it security-relevant.
AI review queuedFinalize stale pending multisig transactions on readby rockstardev · 1bcfc148 · Jul 30, 2026 · 2 filesMessage 50 · ThinLow 40Details
Commit message · rockstardev
Finalize stale pending multisig transactions on read
50/100 · ThinMessage clarity
✓ Specific, 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 40/100
This commit fixes a bookkeeping bug in BTCPay Server's multisig (multi-signature) transaction tracker. Previously, a pending transaction could silently collect enough signatures to be finalized, but the system would still label it as 'Pending' until something else happened. The change makes the service automatically mark such transactions as 'Signed' whenever they are read, and it adds tests to confirm the state is corrected. There is no direct evidence this was a security vulnerability or that it was exploited; it appears to be a state-consistency fix.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a minor code cleanup that simplifies how BTCPay Server writes log messages when a pending multi-signature transaction fails to finalize. It removes the list of failed input indexes from the log and merges two nearly identical log statements into one. There is no security-relevant change.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds more detailed logging when a pending multi-signature Bitcoin transaction fails to finalize. It does not change how transactions are validated, authorized, or executed. There is no security vulnerability being fixed here; it is purely an observability improvement for operators.
AI review queuedFix typoby Nicolas Dorier · 2ed0fa17 · Jul 22, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix typo
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
This commit changes one word in the project's changelog, adding the word 'the' to a bullet point. It is a grammatical typo fix with no effect on software behavior, security, or user data.