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 only reorganizes the project's internal maintainer documentation. It splits one large README into smaller files (coding conventions, local development, Greenfield API) and updates links in related docs and agent skill files. No application code, configuration, or security behavior was changed.
✓ 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 · Informational 15/100
This commit only updates web links and documentation references throughout the BTCPay Server project. It points users to newer, canonical documentation URLs and refreshes local development instructions. There are no code behavior changes, no security fixes, and no vulnerability patches.
AI review queuedUpdate docsby Nicolas Dorier · bc3d8ee4 · Sep 28, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update docs
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
This commit is a one-line documentation update. It adds a hyperlink to the interactive authorization flow in the developer API guide. There is no code change, no security fix, and no functional change to the software.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Informational 15/100
This commit is a large documentation reorganization for BTCPay Server. It moves existing guidance into audience-specific folders (users, operators, developers, maintainers), adds new guides for plugins and API integrations, updates links to point to historical versions of removed docs, and introduces an automated test that checks documentation links and regenerates a configuration reference. There is no code change that affects how BTCPay Server processes payments, stores data, or handles authentication.
Merge pull request #7599 from NicolasDorier/fix/invoice-list-store-permissions
Scope invoice list filters to the current store
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 · Moderate 67/100
This change fixes a permission problem in BTCPay Server's invoice list. Previously, the invoice list page accepted a 'storeid:' search filter or a StoreId parameter that could let a user see invoices from stores they were not supposed to access. The patch forces the invoice list to always use the store ID from the URL route, ignoring any user-supplied store filter, so users can only view invoices for the store they are currently in.
Security candidateContainerize the server settings views into sections (#7501)by dstrukt · 97357e8c · Sep 22, 2026 · 30 filesMessage 58 · ThinInformational 15Details
Commit message · dstrukt
Containerize the server settings views into sections (#7501)
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
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a user-interface redesign, not a security fix. It wraps existing server settings pages into consistent visual sections and adds short explanatory subtitles. No code handling payments, authentication, permissions, or data validation was changed.
AI review queuedRename global search keywords to aliases (#7586)by Nicolas Dorier · 3af94084 · Sep 22, 2026 · 20 filesMessage 53 · ThinInformational 15Details
Commit message · Nicolas Dorier
Rename global search keywords to aliases (#7586)
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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply renames the search feature's 'Keywords' field to 'Aliases' across the BTCPay Server codebase. It is a non-functional refactoring that does not change any security behavior, access controls, or data handling. Backward compatibility is preserved with an obsolete property that maps to the new name.
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 58/100
This commit adds a missing safety check in the API key authorization flow. Previously, if a user clicked a 'confirm' action for an API key that no longer existed, the code would try to use a null (non-existent) key object, which could cause a server crash or unexpected behavior. Now the code checks whether the key exists first and shows an error message if it doesn't.
AI review queuedBump libsby Nicolas Dorier · 48c57151 · Sep 17, 2026 · 4 filesMessage 0 · OpaqueInformational 3Details
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 3/100
This commit simply updates four external software library (NuGet package) versions to newer patch releases. There are no code changes shown, and the commit message gives no indication that any security issue is being fixed. It looks like a routine dependency refresh.
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 35/100
This commit changes how BTCPay Server handles a missing user when an administrator tries to resend a verification email. Previously, the code threw a generic internal error (ApplicationException), which could expose internal details or produce an unhandled error page. Now it returns a clean 'Not Found' response. This is a hardening fix: it improves error handling and reduces information leakage, but it does not by itself grant an attacker new capabilities.
AI review queuedAdd PushNuget.shby Nicolas Dorier · 24f5054e · Sep 7, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Add PushNuget.sh
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit adds a simple build-and-publish helper script for the project's NuGet package. It packages the BTCPayServer.Client library, pushes it to the public NuGet registry using an API key from an environment variable, and creates a matching Git tag. There is no indication this change fixes or introduces a security issue; it is a routine developer tooling addition.
AI review queuedEncode payjoin errors in wallet status messages (#7567)by Nicolas Dorier · a60f8bf2 · Sep 6, 2026 · 1 fileMessage 58 · ThinLow 36Details
Commit message · Nicolas Dorier
Encode payjoin errors in wallet status messages (#7567)
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 36/100
This commit fixes a potential cross-site scripting (XSS) issue in BTCPay Server's wallet status messages. When a payjoin transaction fails, the server shows a warning message that includes an error string. Previously, that error string was inserted directly into the HTML of the status message, so if an attacker could influence the error text to contain malicious code (for example, through a script tag), it could run in the administrator's browser. The change now encodes the error text so that any HTML-like characters are displayed as plain text instead of being interpreted as code.
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 46/100
This commit fixes a bug in BTCPay Server's LNURL feature for pull payments. Previously, if someone requested a LNURL for a pull payment that didn't exist, the code would try to use a null (empty) pull payment object, which could cause the server to crash or behave unpredictably instead of returning a simple 'not found' error. The fix adds a check to return 'not found' if the pull payment is missing.
✓ 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
access controlboot or update path
AI analysis · Informational 15/100
This commit only updates user-facing help text in the Point of Sale plugin. It replaces outdated guidance about legacy API keys and Basic authentication with newer guidance about API tokens and the correct REST API endpoint. No code logic, authentication checks, or security behavior changed.
AI review queuedFix testby Nicolas Dorier · ecfb7990 · Sep 6, 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 adjusts an assertion so that the test now expects a database-migrated API key to have a null CreatedAt value instead of a non-null value. There is no production code change and no security relevance visible in the commit.
This commit refactors how BTCPay Server stores and handles API keys. Previously, the secret API key itself was used as the database primary key, meaning the full secret was stored in plaintext and appeared in URLs/revocation endpoints. Now the system creates a separate public 'key ID' (starting with 'akid_') derived from a hash of the secret, stores only a hash of the secret in the database, and uses the ID for management operations such as revocation. The change also removes the old BitPay 'Basic auth' legacy API key feature entirely. The commit is framed as a security hardening measure, but it is a large refactor rather than a single bug fix.
Security candidateHarden API key storageby Nicolas Dorier · b1294924 · Sep 4, 2026 · 29 filesMessage 28 · OpaqueModerate 60Details
Commit message · Nicolas Dorier
Harden API key storage
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
defensive validationauthentication path
AI analysis · Moderate 60/100
This commit changes how BTCPay Server stores and handles API keys. Previously, the secret API key itself was used as the database primary key and was stored in plaintext. After this change, the database stores a one-way hash of the secret, a short prefix for display, and a separate non-secret ID for management. The actual secret is only kept briefly in memory after creation and is then erased. The commit also removes an old BitPay-compatible 'legacy API key' feature that used Basic authentication with a plaintext key. These are defensive security improvements that reduce the damage if the database is stolen, but they do not by themselves fix an active vulnerability in running code.
AI review queuedbump HtmlSanitizerby Nicolas Dorier · f8946b83 · Sep 4, 2026 · 2 filesMessage 18 · OpaqueLow 32Details
Commit message · Nicolas Dorier
bump HtmlSanitizer
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit updates the HtmlSanitizer library to a newer patch version and reorganizes some account email-change tests. The library bump could fix a security bug in how user-supplied HTML is cleaned, but the commit itself does not say it fixes a security issue or describe any specific vulnerability. The test changes appear to be routine refactoring of how the application verifies email address changes.
AI review queuedRequire current password for account email changesby Nicolas Dorier · f681ec7e · Sep 4, 2026 · 7 filesMessage 50 · ThinModerate 58Details
Commit message · Nicolas Dorier
Require current password for account email changes
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Moderate 58/100
This commit adds a security check so that when a user tries to change their email address on their account profile, they must enter their current password. Before this change, an attacker who had already hijacked a logged-in session could change the account email without proving they knew the password, making account takeover easier. The change is described by the project as low-impact.
AI review queuedMake a signed commitby Nicolas Dorier · e342c62a · Sep 4, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Make a signed commit
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
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.
fix(plugin-manager): use update lookup for installed plugins (#7536)
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Low 35/100
This commit changes how BTCPay Server's plugin manager asks the plugin directory for update information. Previously, the server fetched the full catalog of plugins and then filtered locally. Now it sends a list of the plugins actually installed or pending on the local server and asks only for updates to those. This reduces unnecessary data exposure of the server's plugin inventory to the directory and may avoid bugs where pending or disabled plugins were not considered when checking for updates. It is a hardening/fix change rather than a clear-cut security patch, and the commit message does not claim it fixes a vulnerability.
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.
Prevent monetization from overriding administrator account lockout (#7523)
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
access control
AI analysis · Moderate 61/100
This change fixes a bug where BTCPay Server's paid-subscription ('monetization') system could automatically re-enable an administrator account that had been manually disabled. Previously, when a subscription renewed or was bypassed, the monetization service would call SetDisabled(user, false) without knowing why the account was disabled. The patch adds a 'source' trail so monetization can tell whether it was the one that disabled the account, and it now suspends the subscription instead of overriding an admin lockout. In short: admin-imposed account lockouts can no longer be accidentally undone by billing automation.