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-priorityRequire headless Playwright test runsby Nicolas Dorier · 8fa4f67b · Oct 23, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Nicolas Dorier
Require headless Playwright test runs
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityBump NBitcoin, NBXplorer and .NET dependenciesby Nicolas Dorier · ce14ef89 · Oct 23, 2026 · 11 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Bump NBitcoin, NBXplorer and .NET dependencies
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateKeep shared input limits in syncby Nicolas Dorier · 564d9d0a · Oct 22, 2026 · 27 filesMessage 45 · ThinLow 35Details
Commit message · Nicolas Dorier
Keep shared input limits in sync
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Low 35/100
This commit is a code-quality refactor that moves hard-coded length limits into shared constants so all parts of the app enforce the same limits. It does not add new security checks or remove existing ones, but it fixes places where limits were inconsistent (for example, app names allowed 50 characters in one place and 100 in another). Keeping limits in sync reduces the chance that an attacker could bypass a validation rule by using a different API or UI path.
Lower-priorityMerge pull request #7716 from NicolasDorier/fix/crowdfund-form-routingby Nicolas Dorier · f1148b3e · Oct 22, 2026 · 7 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7716 from NicolasDorier/fix/crowdfund-form-routing
Restore public form routing after validation
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
merge-commit duplicate discount
Lower-priorityMerge pull request #7717 from NicolasDorier/fix/preserve-unresolved-placeholdersby Nicolas Dorier · 312edd85 · Oct 22, 2026 · 8 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7717 from NicolasDorier/fix/preserve-unresolved-placeholders
Preserve unresolved template expressions
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
merge-commit duplicate discount
AI review queuedPreserve unresolved template expressionsby Nicolas Dorier · e0bfaa54 · Oct 22, 2026 · 8 filesMessage 35 · OpaqueLow 35Details
Commit message · Nicolas Dorier
Preserve unresolved template expressions
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 35/100
This commit changes how BTCPay Server fills in template placeholders (like {OrderId} or {InvoiceId}) in URLs, payment descriptions, and point-of-sale button text. Previously, if a placeholder could not be resolved or had a syntax error, it was replaced with a visible error string such as [NotFound(...)] and could also be URL-encoded, making it unreadable. The new behavior preserves the original placeholder expression unchanged when it cannot be resolved, and adds a dedicated URL template helper that properly encodes resolved values while leaving unresolved placeholders intact. The change is described as a fix/polish rather than a security patch, but it reduces the risk of broken or misleading URLs and user-facing strings.
Security candidateMerge pull request #7713 from btcpayserver/security/seed-signing-pending-idby Nicolas Dorier · c8b0876a · Oct 22, 2026 · 4 filesMessage 78 · AdequateModerate 55Details
Commit message · Nicolas Dorier
Merge pull request #7713 from btcpayserver/security/seed-signing-pending-id
Require transaction review for linked seed signing
78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 55/100
This commit changes how BTCPay Server handles signing cryptocurrency transactions with a stored wallet seed. Previously, a user could be sent straight to the seed-signing screen carrying a pre-loaded transaction (a 'pending transaction' and original PSBT). The patch forces that screen to drop any pre-loaded transaction data, so the user must review the transaction before signing. In short, it removes a path that could let an attacker trick someone into signing a transaction they never saw. The rest of the changes are just test and UI tweaks for the Pay Button feature and are not security-related.
Lower-priorityMerge pull request #7715 from NicolasDorier/refactor/use-text-template-placeholdersby Nicolas Dorier · 00d0db57 · Oct 22, 2026 · 8 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7715 from NicolasDorier/refactor/use-text-template-placeholders
Use TextTemplate for placeholder rendering
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
merge-commit duplicate discount
Lower-priorityMerge pull request #7714 from NicolasDorier/fix/validate-invoice-redirect-urlby Nicolas Dorier · 08c7928a · Oct 22, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7714 from NicolasDorier/fix/validate-invoice-redirect-url
Validate invoice redirect URL schemes
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 queuedUse TextTemplate for placeholder renderingby Nicolas Dorier · cc4adca4 · Oct 22, 2026 · 8 filesMessage 25 · OpaqueLow 45Details
Commit message · Nicolas Dorier
Use TextTemplate for placeholder rendering
25/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Low 45/100
This commit replaces several hand-written string-replacement routines with a shared TextTemplate engine for rendering placeholders in URLs, emails, Lightning payment descriptions, and point-of-sale button text. The change is a defensive refactoring: it centralizes how user-supplied values are substituted into templates, making it easier to ensure values are encoded consistently. The new test shows that URL placeholders are now URL-encoded, which reduces the risk of malicious values breaking or manipulating generated links. There is no direct evidence in the commit of an exploitable vulnerability being fixed, but the change removes a common source of injection and encoding mistakes.
Lower-priorityReject unsafe invoice redirect URLsby Nicolas Dorier · 61c72298 · Oct 22, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Reject unsafe invoice redirect URLs
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateReject workflow state from seed signing linksby Nicolas Dorier · f3481aa5 · Oct 22, 2026 · 4 filesMessage 45 · ThinModerate 57Details
Commit message · Nicolas Dorier
Reject workflow state from seed signing links
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 57/100
This commit changes how BTCPay Server handles wallet signing links that use a stored seed. Previously, clicking a 'seed' signing link could automatically carry over a pending transaction and original PSBT (a partially-signed Bitcoin transaction) from the user's workflow state. The patch makes the seed signing page discard that workflow state and only accept signing context supplied directly in the link. This likely closes a security issue where a malicious or crafted link could trick a user into signing a different transaction than expected by reusing state from a previous session.
AI review queuedMerge pull request #7711 from comwanga/fix/fast-test-ci-discovery-7710by Nicolas Dorier · 419f96ca · Oct 21, 2026 · 4 filesMessage 83 · StrongInformational 15Details
Commit message · Nicolas Dorier
Merge pull request #7711 from comwanga/fix/fast-test-ci-discovery-7710
test: restore CI coverage for FastTest-tagged tests
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
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only changes test labels from 'FastTest' to 'Fast' in four test files. It restores which automated tests run in the project's fast/CI test suite. There is no change to production code, user-facing behavior, or security functionality.
AI review queuedtest: restore CI coverage for seven fast testsby comwanga · 4edd34e7 · Oct 21, 2026 · 4 filesMessage 67 · AdequateInformational 15Details
Commit message · comwanga
test: restore CI coverage for seven fast tests
67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only renames test category labels from 'FastTest' to 'Fast' in seven automated tests. It does not change any production code, user-facing behavior, or security logic. The change is purely to restore these tests running in the project's continuous integration (CI) pipeline.
Lower-priorityMerge pull request #7690 from btcpayserver/fix/email-recipient-hardeningby Nicolas Dorier · 42df05ed · Oct 21, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7690 from btcpayserver/fix/email-recipient-hardening
Harden email rule recipients
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-priorityHarden email rule recipientsby Andrew Camilleri (Kukks) · fabd4fce · Oct 21, 2026 · 2 filesMessage 50 · ThinTriage 8Details
Commit message · Andrew Camilleri (Kukks)
Harden email rule recipients
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>
50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Why it was queued
defensive validation
Lower-priorityShow diagnostics for automatically disabled plugins (#7708)by Nicolas Dorier · 0e53c531 · Oct 21, 2026 · 10 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Show diagnostics for automatically disabled plugins (#7708)
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 #7707 from NicolasDorier/fix/invoice-store-created-indexby Nicolas Dorier · dadea65b · Oct 21, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7707 from NicolasDorier/fix/invoice-store-created-index
Improve store invoice query performance
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-priorityAdd store invoice creation indexby Nicolas Dorier · 849b5d5b · Oct 21, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Add store invoice creation index
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge pull request #7706 from Psycarlo/fix/greenfield-pay-null-paymentby Nicolas Dorier · acc6872b · Oct 21, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7706 from Psycarlo/fix/greenfield-pay-null-payment
fix: handle a null payment after a Greenfield Lightning pay
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
merge-commit duplicate discount
Lower-priorityfix: handle a null payment after a Greenfield Lightning payby psycarlo · eff448ca · Oct 20, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · psycarlo
fix: handle a null payment after a Greenfield Lightning pay
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityMerge pull request #7704 from NicolasDorier/fix/logout-postby Nicolas Dorier · d684c2c4 · Oct 20, 2026 · 6 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7704 from NicolasDorier/fix/logout-post
Require POST for logout
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 queuedRequire POST for logoutby Nicolas Dorier · 0747c704 · Oct 20, 2026 · 6 filesMessage 28 · OpaqueModerate 52Details
Commit message · Nicolas Dorier
Require POST for logout
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 52/100
This change makes the logout action require a POST request instead of a simple link click (GET). The old GET-based logout could potentially be triggered by a malicious web page tricking a logged-in user's browser into visiting the /logout URL, logging them out unexpectedly. By switching to a POST form button, the logout can no longer be triggered by a simple embedded link or image, which is a standard defense against cross-site request forgery (CSRF)-style logout attacks. The patch also updates tests and navigation UI to use the new POST form.
Lower-priorityMerge pull request #7696 from btcpayserver/fix/form-input-hardeningby Nicolas Dorier · 0fe158d5 · Oct 20, 2026 · 8 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7696 from btcpayserver/fix/form-input-hardening
Harden public form values
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
This commit hardens how BTCPay Server handles public web forms used during checkout, such as crowdfunding and point-of-sale purchases. Before the fix, shoppers could tamper with hidden or visible form fields to change prices, add bogus fees, inject oversized data, or overwrite server-only values. The patch now forces the real price to be set after the user submits the form but before validation, rejects non-numeric amount adjustments, clears values that should be server-controlled, caps text field lengths at 10,000 characters, and adds tests showing these tampering attempts are now blocked.