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.
Lower-priorityAdd Greenfield API for reports (#7608)by Nicolas Dorier · 7f808e34 · Sep 29, 2026 · 14 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Add Greenfield API for reports (#7608)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
✓ 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.
Lower-priorityMove invoice, translation, and metadata guides into core (#7606)by Nicolas Dorier · b2c308ed · Sep 28, 2026 · 19 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Move invoice, translation, and metadata guides into core (#7606)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Fix missing global search documentation image (#7605)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
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.
Lower-priorityScope invoice list to current storeby Nicolas Dorier · fdfdbb20 · Sep 25, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Scope invoice list to current store
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Handle reused payment destinations during invoice creation (#7483)
Co-authored-by: anton <anton@gm.lan>
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 and NBXplorer test images (#7596)by Nicolas Dorier · a8bc1262 · Sep 25, 2026 · 4 filesMessage 63 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Bump Tor and NBXplorer test images (#7596)
63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityWarn when Docker LND API routes are disabled (#7593)by Nicolas Dorier · 8911779f · Sep 24, 2026 · 9 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Warn when Docker LND API routes are disabled (#7593)
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-priorityBound test host shutdown time (#7592)by Nicolas Dorier · 04024ccf · Sep 23, 2026 · 8 filesMessage 63 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Bound test host shutdown time (#7592)
63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityUse configured base URL for callback links (#7590)by Nicolas Dorier · 37861125 · Sep 22, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Use configured base URL for callback links (#7590)
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 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.
Merge pull request #7589 from btcpayserver/remove-test-tor-host-ports
Stop exposing test Tor ports on host
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
Why it was queued
merge-commit duplicate discount
Lower-priorityStop exposing test Tor ports on hostby Nicolas Dorier · 8ee9d341 · Sep 22, 2026 · 4 filesMessage 55 · ThinTriage 0Details
Commit message · Nicolas Dorier
Stop exposing test Tor ports on host
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Run migrations for plugin database contexts (#7588)
* Run custom plugin database migrations
* Remove migration registration test
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
Lower-priorityShow test progress in CI (#7587)by Nicolas Dorier · c46e90fd · Sep 22, 2026 · 3 filesMessage 63 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Show test progress in CI (#7587)
63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body