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.
AI review queuedFix flaky email testby Nicolas Dorier · 484fe96e · Oct 6, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix flaky email 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 a single line to a test file to wait for a web page element to appear before interacting with it. It is a test reliability fix only and does not change any production code, user-facing behavior, or security boundary.
Lower-priorityAllow SSRF exceptions for private servicesby Nicolas Dorier · 65a167bd · Oct 6, 2026 · 9 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Allow SSRF exceptions for private services
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityEnhance PR description guidelines in SKILL.mdby Nicolas Dorier · b75bed02 · Oct 6, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Enhance PR description guidelines in SKILL.md
Added detailed guidelines for writing pull request descriptions, including required context and formatting instructions for GitHub CLI.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
Lower-priorityDeprecate invoice notification URLs (#7647)by Nicolas Dorier · 5bf538d4 · Oct 6, 2026 · 4 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Deprecate invoice notification URLs (#7647)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedSmall refactoringby Nicolas Dorier · eba60702 · Oct 6, 2026 · 2 filesMessage 18 · OpaqueLow 45Details
Commit message · Nicolas Dorier
Small refactoring
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 · Low 45/100
This commit tweaks how BTCPay Server blocks internal/private network addresses when making outbound connections (an SSRF protection feature). Previously, if any resolved address was private, the whole request was rejected. Now, the code skips private addresses and tries only public ones. If no public address exists, it still rejects the request. The change is described by the author as a small refactoring, but it alters the security behavior slightly: a hostname that resolves to both public and private addresses will now connect to the public address instead of failing outright. The tests were updated only to match the new error message.
AI review queuedRefactor SSRFby Nicolas Dorier · ed51828a · Oct 6, 2026 · 8 filesMessage 18 · OpaqueLow 45Details
Commit message · Nicolas Dorier
Refactor SSRF
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 · Low 45/100
This commit is a code cleanup that changes how BTCPay Server blocks outgoing requests to internal/local network addresses (SSRF protection). It moves the protection logic from a shared service into an extension method used when configuring HTTP clients. The change appears intended to be behavior-preserving, but it removes some unit tests that previously verified the protection works for Bitpay and Webhook clients. Because the patch is only a refactor and no vulnerability is introduced in the diff, this is not a clear security issue on its own, though removing tests reduces future assurance.
Lower-priorityProtect webhook requests from SSRF (#7646)by Nicolas Dorier · cac6a2b1 · Oct 5, 2026 · 6 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Protect webhook requests from SSRF (#7646)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedFix flaky testby Nicolas Dorier · 9afe7e80 · Oct 5, 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 one-line change in an automated test file. It makes the test wait for a web page modal to be fully visible before clicking a button, which should make the test less likely to fail randomly. There is no change to production code and no security relevance.
Lower-priorityProtect invoice IPN requests from SSRF (#7644)by Nicolas Dorier · ec3d4205 · Oct 5, 2026 · 2 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Protect invoice IPN requests from SSRF (#7644)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Security candidateAdd dedicated permission and CSRF protection for invoice status changes (#7643)by Nicolas Dorier · 36d4d8b2 · Oct 5, 2026 · 10 filesMessage 58 · ThinHigh 74Details
Commit message · Nicolas Dorier
Add dedicated permission and CSRF protection for invoice status changes (#7643)
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
credential or privilege stateauthentication path
AI analysis · High 74/100
This commit hardens BTCPay Server's invoice status changes. Previously, marking an invoice as settled or invalid required the broad 'modify invoices' permission and the web UI action ignored CSRF protection. The patch adds a dedicated, narrower permission for status changes and requires anti-forgery validation on the web UI endpoint, reducing the risk that a malicious web page or overly permissioned API key can flip invoice states.
Lower-priorityScope payout payments to current store (#7642)by Nicolas Dorier · 9238d6bb · Oct 5, 2026 · 2 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Scope payout payments to current store (#7642)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Security candidateUpdate Google Cloud credential loadingby Nicolas Dorier · 3f9bcabf · Oct 5, 2026 · 1 fileMessage 45 · ThinInformational 24Details
Commit message · Nicolas Dorier
Update Google Cloud credential loading
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Informational 24/100
This commit changes how BTCPay Server loads Google Cloud service-account credentials. It switches from a general Google credential parser to a more specific service-account credential parser. The change is likely a hardening or compatibility fix, but the commit message gives no security context, so we cannot tell whether it fixes a known vulnerability or is just routine maintenance.
Lower-priorityFix payout completion after RBFby Nicolas Dorier · 82ab71b3 · Oct 5, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Fix payout completion after RBF
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedBump dependenciesby Nicolas Dorier · 03c8d8a2 · Oct 5, 2026 · 7 filesMessage 18 · OpaqueLow 29Details
Commit message · Nicolas Dorier
Bump dependencies
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 · Low 29/100
This commit updates many third-party software libraries used by BTCPay Server to newer versions. The changes also adjust how FIDO2/WebAuthn security-key support is configured to match the newer library. Dependency bumps can fix security bugs in those libraries, but the commit message does not say which bugs are being fixed, and the diff itself does not show any direct security patch in BTCPay Server's own code.
Lower-priorityFix flaky monetization bypass test teardown (#7639)by Nicolas Dorier · 94c87f58 · Oct 5, 2026 · 4 filesMessage 68 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Fix flaky monetization bypass test teardown (#7639)
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
Lower-priorityBump BTCPayServer.Lightning to 1.7.12by Nicolas Dorier · 185f9251 · Oct 5, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Bump BTCPayServer.Lightning to 1.7.12
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityProtect LNURL HTTP requests from SSRFby Nicolas Dorier · 8d2afc91 · Oct 5, 2026 · 6 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Protect LNURL HTTP requests from SSRF
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityVerify Lightning HTTP endpoints when connecting (#7637)by Nicolas Dorier · 2d1419ee · Oct 5, 2026 · 17 filesMessage 68 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Verify Lightning HTTP endpoints when connecting (#7637)
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
Lower-priorityPersist Lightning unsafe endpoint approvalby Nicolas Dorier · f7e7888f · Oct 5, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Persist Lightning unsafe endpoint approval
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityHarden Lightning connection validation (#7635)by Nicolas Dorier · 8e96a656 · Oct 5, 2026 · 6 filesMessage 53 · ThinTriage 8Details
Commit message · Nicolas Dorier
Harden Lightning connection validation (#7635)
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✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
fuzzing or regression evidence
Lower-priorityAvoid fetching Lightning node info for invoices (#7633)by Nicolas Dorier · e4418f65 · Oct 4, 2026 · 7 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Avoid fetching Lightning node info for invoices (#7633)
58/100 · ThinMessage clarity
✓ Specific, 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✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Low 28/100
This commit renames a permission that controls who can manage old-style BitPay-compatible access tokens. The old name, 'Manage access tokens,' sounded like it applied to modern API keys, but it only ever applied to legacy BitPay tokens. The new name, 'Manage legacy access tokens,' makes that clear. The change is mostly a labeling and code-organization cleanup; it does not appear to add or remove any actual security checks, but it may reduce confusion that could lead to users granting more access than intended.
Lower-priorityPersist Lightning replacements before canceling old invoices (#7630)by Nicolas Dorier · f17652cd · Oct 4, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Persist Lightning replacements before canceling old invoices (#7630)
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-priorityValidate configured request base URL schemes (#7628)by Nicolas Dorier · c78aa2b9 · Oct 4, 2026 · 2 filesMessage 58 · ThinTriage 8Details
Commit message · Nicolas Dorier
Validate configured request base URL schemes (#7628)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body