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-priorityKeep token revocation redirects in the current store (#7629)by Nicolas Dorier · 10f525f9 · Oct 4, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Keep token revocation redirects in the current store (#7629)
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-priorityMerge pull request #7627 from NicolasDorier/fix/lndhub-connection-string-safetyby Nicolas Dorier · eb76d1b8 · Oct 4, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7627 from NicolasDorier/fix/lndhub-connection-string-safety
Validate LNDHub connection string endpoints
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Lower-priorityValidate LNDHub connection string endpointsby Nicolas Dorier · 01aa8c42 · Oct 4, 2026 · 2 filesMessage 45 · ThinTriage 8Details
Commit message · Nicolas Dorier
Validate LNDHub connection string endpoints
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 #7626 from NicolasDorier/improve-internal-network-detectionby Nicolas Dorier · 7fe7187f · Oct 4, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7626 from NicolasDorier/improve-internal-network-detection
Improve internal network detection
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
AI review queuedImprove internal network detectionby Nicolas Dorier · e3e29dc0 · Oct 4, 2026 · 2 filesMessage 35 · OpaqueModerate 63Details
Commit message · Nicolas Dorier
Improve internal network detection
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 63/100
This commit rewrites how BTCPay Server decides whether a network address is 'internal' versus 'public'. The old check only recognized a few private ranges (local loopback and RFC1918). The new check recognizes many more special-use ranges, such as carrier-grade NAT, link-local, documentation/test IPs, multicast, and IPv6 equivalents. The change is framed as a hardening improvement, but the commit message does not explicitly call it a security fix. If the old code was used to block or restrict access to internal services, the previous gaps could have let an attacker trick the server into treating an internal address as public, potentially enabling Server-Side Request Forgery (SSRF) or similar attacks. However, the diff alone does not show a specific vulnerable call site or exploit path.
Lower-priorityMerge pull request #7624 from btcpayserver/warn-legacy-access-tokensby Nicolas Dorier · 973fb804 · Oct 3, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7624 from btcpayserver/warn-legacy-access-tokens
Warn against legacy access tokens
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-priorityWarn against legacy access tokensby Nicolas Dorier · a15953a0 · Oct 3, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Warn against legacy access tokens
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge pull request #7623 from NicolasDorier/fix-api-key-checkbox-redisplayby Nicolas Dorier · a1d509d1 · Oct 2, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7623 from NicolasDorier/fix-api-key-checkbox-redisplay
Fix API key form checkbox redisplay
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-priorityFix API key form checkbox redisplayby Nicolas Dorier · 54dd1e27 · Oct 2, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Fix API key form checkbox redisplay
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedAdd 2.4.5 changelogby Nicolas Dorier · 0cb14ec7 · Oct 2, 2026 · 1 fileMessage 38 · OpaqueHigh 79Details
Commit message · Nicolas Dorier
Add 2.4.5 changelog
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
This commit only adds a changelog entry for BTCPay Server version 2.4.5. The changelog itself describes several security-related fixes and one breaking change that blocks private-network outbound requests by default to prevent server-side request forgery (SSRF). It also mentions fixes for invoice search scoping, antiforgery validation, payout scoping, refund permissions, and URL validation. Because the commit is just documentation summarizing prior changes, the direct code risk is low, but the listed changes indicate that the 2.4.5 release addresses multiple security issues.
AI review queuedDummy commitby Nicolas Dorier · 8bb7d8ee · Oct 2, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Dummy commit
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 only reformats code and adds blank lines in a single controller file. No behavior, logic, or security checks were changed. It is a non-functional 'dummy' style/refactoring commit with no security relevance.
Lower-priorityMerge pull request #7621 from NicolasDorier/bump-btcpayserver-lightning-1.7.11by Nicolas Dorier · 3c8289eb · Oct 2, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7621 from NicolasDorier/bump-btcpayserver-lightning-1.7.11
Bump BTCPayServer.Lightning libraries
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
AI review queuedBump BTCPayServer.Lightning librariesby Nicolas Dorier · a92e8f9e · Oct 2, 2026 · 2 filesMessage 35 · OpaqueInformational 4Details
Commit message · Nicolas Dorier
Bump BTCPayServer.Lightning libraries
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 4/100
This commit only updates two internal library version numbers (BTCPayServer.Lightning.Common from 1.7.2 to 1.7.3 and BTCPayServer.Lightning.All from 1.7.10 to 1.7.11). No code changes are included, and the commit message does not mention any security fix. Without knowing what changed in those external libraries, this diff alone does not show any security issue or fix.
Lower-priorityShare the installed-languages dropdown helper through LocalizerService (#7601)by Roxanne · 125b2c9d · Oct 2, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Roxanne
Share the installed-languages dropdown helper through LocalizerService (#7601)
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-priorityLightning setup and settings pages always use the store the user is authorized for (#7618)by Team1 · 3365125f · Oct 2, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Team1
Lightning setup and settings pages always use the store the user is authorized for (#7618)
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-prioritySkip MCP plugin compatibility buildby Nicolas Dorier · 31846348 · Oct 2, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Skip MCP plugin compatibility build
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #7619 from NicolasDorier/bump-version-dependenciesby Nicolas Dorier · 20f19574 · Oct 1, 2026 · 9 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7619 from NicolasDorier/bump-version-dependencies
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
AI review queuedBump version and dependenciesby Nicolas Dorier · 415625c1 · Oct 1, 2026 · 9 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Bump version and dependencies
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine version bump for the BTCPay Server application and updates several third-party software libraries and build tools to newer patch versions. There is no indication in the commit itself that this is a security fix, and no security-relevant code changes are present.
AI review queuedUpdate translation stringsby Nicolas Dorier · fbcfbc8e · Oct 1, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update translation strings
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only updates translation strings in a localization file and removes a trailing newline from a Swagger JSON file. There are no code behavior changes, no security fixes, and no functional modifications.
Lower-priorityUpdate admin store access testby Nicolas Dorier · fd333b41 · Oct 1, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Nicolas Dorier
Update admin store access test
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Security candidateMerge pull request #7612 from minmoto/okjodom/store-credentials-permissionby Nicolas Dorier · a0319215 · Oct 1, 2026 · 10 filesMessage 73 · AdequateModerate 51Details
Commit message · Nicolas Dorier
Merge pull request #7612 from minmoto/okjodom/store-credentials-permission
Add store permission for managing access tokens
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 51/100
This change introduces a new, more specific permission called 'Manage access tokens' for store-level access token operations in BTCPay Server. Previously, viewing tokens required the broad 'View store settings' permission and creating or revoking tokens required the even broader 'Modify store settings' permission. The patch narrows those checks so that token management now uses its own dedicated permission. The new permission is automatically granted to the built-in 'Manager' role, and it is included by the existing 'Modify store settings' permission, so users who already had full store control keep the same access. This is a security hardening change that reduces the risk of lower-privileged users (for example, guests or employees) being able to create or revoke API access tokens if they had been accidentally given overly broad store settings rights.
Lower-priorityRestore canonical wallet setup linkby Nicolas Dorier · 98e0b131 · Oct 1, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Restore canonical wallet setup link
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Introduce btcpay.store.canmanagestorecredentials, included by btcpay.store.canmodifystoresettings and granted to the built-in Manager role. Store access tokens, pairing, and their navigation now require it, so roles such as Guest no longer see or manage a store's access tokens.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
credential or privilege state
AI analysis · Moderate 51/100
This change adds a new, more specific permission for managing store access tokens in BTCPay Server. Previously, viewing or managing these tokens required only broad 'view store settings' or 'modify store settings' permissions, which meant lower-privileged roles like Guest could see or manage them. Now, a dedicated 'manage store credentials' permission is required, and it is automatically granted to the built-in Manager role. This is a hardening fix that reduces the risk of privilege misuse, but it is not a patch for a known active exploit.
✓ 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 pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This commit is a code cleanup and developer-experience improvement for how BTCPay Server plugins manage their PostgreSQL databases. It introduces a shared helper and base class so plugin authors no longer need to manually wire up database connections, retry logic, and migration history tables. There is no obvious security bug introduced, but any change to database setup code can affect reliability and migration behavior, so it warrants a careful look rather than being dismissed as purely cosmetic.
AI review queuedAdd maintainer docby Nicolas Dorier · 69c44f1e · Sep 29, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Add maintainer doc
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit adds a single sentence to an internal maintainer documentation file, instructing maintainers to also update a separate documentation repository when changing documentation structure. It does not modify any code, configuration, or security policy.