CommitWatch RSS
BT
← All projectsBTCPay Server

BTCPay Server

Free, open-source, self-hosted Bitcoin payment processor supporting on-chain and Lightning payments.

BitcoinLightning NetworkPayment infrastructureNormal
Source repository ↗Security policy ↗
Repository coverage

661 commits in the local evidence base

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.

85security candidates223second-pass queue308AI analyses
94commits · 30 days
118commits · 60 days
315commits · 180 days
634commits · 365 days
Backfill bands
Aug 8 → Feb 9247 seen22 candidatesComplete
Feb 9 → Jun 9197 seen39 candidatesComplete
Jun 9 → Jul 954 seen0 candidatesComplete
Jul 9 → Aug 865 seen16 candidatesComplete
Commit communication

Does the history explain itself?

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
80Strong · 80–100
148Adequate · 60–79
277Thin · 40–59
156Opaque · 0–39
8security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Nicolas Dorier43748226346
Cerberus622290
ndeet111133
rockstardev33612049
Abhijay Jain26610087
Chukwuleta Tobechi25610068
thgO.O32512066
dstrukt625062
Tim522074
Atharva Borade711067
Pavlenex412065
psam21312068
Analysis record

Published AI watches

Last scanned 7 minutes ago

Informational 15 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Containerize the server settings views into sections (#7501)

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 val…

97357e8cby dstrukt+255−11230 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 53 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Rename global search keywords to aliases (#7586)

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 com…

3af94084by Nicolas Dorier+96−7720 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 58 AI analysisMessage 36 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

fix confirm (#7570)

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 caus…

Null dereference / NullReferenceException preventedMissing validation of repository return valueUser-facing authorization flow hardening
bd7f91e2by monasco+9−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 3 AI analysisMessage 0 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Bump libs

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…

48c57151by Nicolas Dorier+5−54 files
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 36 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

fix notfound (#7572)

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 pro…

Replaces thrown ApplicationException with NotFound() for missing userReduces information leakage via exception message containing userIdImproves HTTP semantics (404 instead of 500-class error)
491cf201by monasco+1−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Add PushNuget.sh

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 mat…

24f5054eby Nicolas Dorier+16−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 36 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Encode payjoin errors in wallet status messages (#7567)

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…

HTML content constructed from an external error string without encodingAddition of HtmlEncoder.Default.Encode around user-influenced or third-party error textStatus message rendered as raw Html in the UI
a60f8bf2by Nicolas Dorier+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 46 AI analysisMessage 36 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

fix lnurl (#7563)

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 …

Null dereference / missing null check on database/service lookup resultPotential server-side exception (DoS/crash) on crafted LNURL requestInformation disclosure risk if exception details leak stack traces
227912f2by monasco+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 63 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update POS callback authentication guidance (#7566)

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,…

045f70a2by Nicolas Dorier+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 0 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix test

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 relev…

ecfb7990by Nicolas Dorier+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 56 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge branch 'refact-api-keys'

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…

API key secrets no longer used as database primary key or in revocation URLsDatabase now stores SHA256 hash of secret rather than plaintext secret for authentication lookupNew ephemeral Key column cleared after 5 minutes by scheduled cleanup
7ec0260bby Nicolas Dorier+368−39129 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 28 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Harden API key storage

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,…

Database now stores SHA-256 hash of API key secret instead of the secret itselfAPI key secret is cleared from database after creation via scheduled cleanup jobPublic management ID (akid_*) is separated from the secret
b1294924by Nicolas Dorier+368−39129 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 32 AI analysisMessage 18 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

bump HtmlSanitizer

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 f…

Dependency version bump of an HTML-sanitization library (HtmlSanitizer)Test-only reorganization around account email change flowsNo explicit security advisory, CVE, or vulnerability description in commit message
f8946b83by Nicolas Dorier+17−332 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 58 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Require current password for account email changes

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 …

Account-takeover mitigation: email change now requires password re-authenticationNew model property CurrentPassword with DataType.PasswordController now calls CheckPasswordAsync before applying email change
f681ec7eby Nicolas Dorier+74−137 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Make a signed commit

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.

e342c62aby Nicolas Dorier+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 70 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

fix(plugin-manager): use update lookup for installed plugins (#7536)

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 inst…

Reduces information disclosure to external plugin directory by sending only installed/pending plugin list instead of querying full catalogAdds input validation on plugin update response (null entries, missing identifier/version)Improves handling of disabled and pending plugins in update checks
c617a24fby thgO.O+248−685 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 38 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix flaky test

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.

34ce3589by Nicolas Dorier+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 38 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix github reports in CI

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.

4208bf71by Nicolas Dorier+15−11 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 66 AI analysisMessage 85 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Validate support URL scheme to prevent stored script injection (#7537)

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 en…

Stored XSS via javascript: URI in SupportUrlMissing scheme validation on user-supplied URLGreenfield API and UI controller both patched
a6b81460by Chukwuleta Tobechi+19−33 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 61 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Prevent monetization from overriding administrator account lockout (#7523)

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 mo…

Privilege/authorization bypass: automated subsystem overriding an administrative account-disable actionMissing provenance/audit trail in security-sensitive state change (account disabled flag)Business-logic flaw in subscription lifecycle interacting with identity lockout
0e4fc389by Chukwuleta Tobechi+28−64 files
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidatePoS: Any store users can now generate a login QR any other store user (#7303)by Nicolas Dorier · 5062be43 · Apr 9, 2026 · 8 filesMessage 58 · ThinModerate 66Details
Commit message · Nicolas Dorier

PoS: Any store users can now generate a login QR any other store user (#7303)

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
boot or update path
AI analysis · Moderate 66/100

This commit changes how login QR codes are generated for BTCPay Server's Point of Sale (PoS) feature. Previously, only store owners or admins could generate login codes, and there was a warning when selecting a store owner. After this change, any store user can generate a login QR code for any other store user, including store owners, without the previous confirmation step. The commit title itself says this is intentional: 'Any store users can now generate a login QR any other store user.' This appears to be a deliberate feature change, but it weakens access controls around sensitive login credentials.

Security candidatePoS: Unpermissioned store users can browse login links and invoices from Update PoS page (#7305)by Nicolas Dorier · 910cc48b · Apr 9, 2026 · 4 filesMessage 58 · ThinModerate 68Details
Commit message · Nicolas Dorier

PoS: Unpermissioned store users can browse login links and invoices from Update PoS page (#7305)

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 stateboot or update path
AI analysis · Moderate 68/100

This update fixes a permissions issue in BTCPay Server's Point of Sale (PoS) settings page. Previously, store users who only had permission to view settings—but not modify them—could still load the 'Update Point of Sale' page and see sensitive things like invoice lists and login links. The fix makes the page read-only for those users by disabling or hiding edit controls unless the user has modify-permissions. The same permission helper was also extended to cover more HTML elements (buttons, inputs, divs), and a small navigation markup cleanup was done for Crowdfund and PoS menus.

Lower-priorityAPI/Subscriptions: Add update offering plan (#7297)by Nicolas Dorier · b7e358bf · Apr 6, 2026 · 5 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier

API/Subscriptions: Add update offering plan (#7297)

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-priorityAPI/Subscriptions: Add update offering route (#7296)by Nicolas Dorier · 52ba2c9d · Apr 6, 2026 · 7 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier

API/Subscriptions: Add update offering route (#7296)

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-priorityAvoid hardcoded default value in UpdateCrowdfundAppby Nicolas Dorier · b5c20389 · Apr 6, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Avoid hardcoded default value in UpdateCrowdfundApp

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityIncrease timeout for migrations through DIby Nicolas Dorier · ae8120d7 · Apr 2, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Increase timeout for migrations through DI

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedChangelog 2.3.7by Nicolas Dorier · b0373f2e · Apr 2, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Changelog 2.3.7

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds a new section to the project's Changelog.md file describing version 2.3.7. It lists new features and bug fixes but does not change any application code, configuration, or security settings. There is nothing in this commit that could directly affect security.

Lower-priorityFix: Invoice cleanup task could timeout if there was too many invoices (#7291)by Nicolas Dorier · 71353bbf · Apr 2, 2026 · 7 filesMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Invoice cleanup task could timeout if there was too many invoices (#7291)

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
AI review queuedUpdate translationsby Nicolas Dorier · f0923857 · Apr 1, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Update translations

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
translation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates translation strings in a single C# file. It adds, removes, and reorders user-facing text labels (for example, new labels for subscription dates and recovery codes). There are no code logic changes, no security fixes, and no functional behavior changes visible in the diff.

Lower-priorityfix: exclude trial subscribers from monthly revenue (#7273)by Abhijay Jain · c78d716d · Apr 1, 2026 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · Abhijay Jain

fix: exclude trial subscribers from monthly revenue (#7273)

* fix: exclude trial subscribers from monthly revenue

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* fix: avoid Trial filter placement changes subscriber counts

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

---------

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityFix: Websocket connection in checkout was failing due to CSRFby Nicolas Dorier · c8ed2c6d · Mar 31, 2026 · 1 fileMessage 74 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Websocket connection in checkout was failing due to CSRF

74/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Explains rationale or failure mode! No meaningful explanatory body
AI review queuedfeat: add ability to add comment to the transaction on the send view (#7265)by Abhijay Jain · f07553b6 · Mar 31, 2026 · 6 filesMessage 85 · StrongInformational 15Details
Commit message · Abhijay Jain

feat: add ability to add comment to the transaction on the send view (#7265)

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ 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 adds a simple optional comment field to the wallet send screen in BTCPay Server. Users can type a short note (up to 200 characters) when preparing a transaction, and that note is saved alongside the transaction after it is broadcast. There is no security issue visible in the change.

Security candidatefeat: add manual subscription date editing for admins (#7257)by Abhijay Jain · 8ceb55cd · Mar 31, 2026 · 9 filesMessage 100 · StrongLow 30Details
Commit message · Abhijay Jain

feat: add manual subscription date editing for admins (#7257)

* feat: add manual subscription date editing for admins

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: Address code review feedback on subscription date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: Use DateOnly params and normalize to UTC for date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: added tests and API route

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: addressed coding suggestions

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: added null check

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* docs: updated swagger todocument manual subscription date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* Slight adjustment

---------

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update path
AI analysis · Low 30/100

This commit adds a new admin-only feature that lets store administrators manually edit subscription start and expiration dates for subscribers, both through the web interface and the API. It is a normal feature addition, not a vulnerability fix. The code includes basic validation (expiration must be after start) and is restricted to users who already have permission to manage subscribers. There is no direct evidence in the commit that this introduces a security bug, but any date-editing feature could theoretically be misused by a compromised admin account or through authorization bugs.

Lower-priorityFix: If an admin was accessing user's store from user list, it was returning error 404by Nicolas Dorier · f5b9198d · Mar 30, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: If an admin was accessing user's store from user list, it was returning error 404

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritylightning: support amountless bolt11 for top-up invoices (#7263)by bigg-bb · ca9a2612 · Mar 30, 2026 · 5 filesMessage 91 · StrongTriage 0Details
Commit message · bigg-bb

lightning: support amountless bolt11 for top-up invoices (#7263)

* lightning: support amountless bolt11 for top-up invoices

Made-with: Cursor

* test: Enhance lightning payment method assertions in CheckoutUITests and PlaywrightTests

Updated assertions to verify that lightning payment URLs and addresses can start with either 'lnurl' or 'lnbcrt'. Improved error messages for clarity and ensured consistency in handling payment method comments in PlaywrightTests.

* fixed reviewd changes

* retrigger CI

* retrigger CI

* Remove redundant check for amountless BOLT11 in displayed payment methods as topup amountless invoices are supported

* fixed test cases

* test fix for topup lnurl

* test: Update payment method assertions in CheckoutUITests and PlaywrightTests

Modified assertions to reflect the correct display of payment methods, changing "LNBCRT" to "Lightning" in CheckoutUITests. Removed redundant null check for BOLT11 minimum amount in PlaywrightTests to streamline the test logic.

* fix

* fix

* fixed test cases one more time

* Improve test

---------

Co-authored-by: bigg-bb <bigg-bb@users.noreply.github.com>
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Security candidateDev: Helps Rider to find Layouts properly (#7283)by Nicolas Dorier · c0e58290 · Mar 27, 2026 · 21 filesMessage 53 · ThinInformational 15Details
Commit message · Nicolas Dorier

Dev: Helps Rider to find Layouts properly (#7283)

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
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a developer-experience tweak. It changes how Razor view files reference their page layouts so that the JetBrains Rider IDE can find them more reliably. It also updates a test assertion style and bumps the C# language version from 12 to 14. There is no security-relevant change.

AI review queuedFix flaky testsby Nicolas Dorier · 90a91c4d · Mar 26, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flaky tests

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 fixes a timing issue in BTCPay Server's automated test suite. It ensures that when a test triggers a browser alert dialog, the test waits for the dialog to actually be accepted before continuing. Previously, the test could proceed before the dialog handler finished, causing unpredictable 'flaky' test failures. There is no change to production code or user-facing security behavior.

AI review queuedFix possible race condition when updating a PaymentRequest (#7281)by Nicolas Dorier · 8ffba4f8 · Mar 26, 2026 · 2 filesMessage 58 · ThinLow 35Details
Commit message · Nicolas Dorier

Fix possible race condition when updating a PaymentRequest (#7281)

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
second-pass: broader security terminology
AI analysis · Low 35/100

This commit fixes a potential race condition in how BTCPay Server updates the status of a Payment Request. Previously, the code read the record, changed its status in memory, and saved it back. If two processes did this at the same time, one update could overwrite the other, possibly causing duplicate or missed events. The fix uses a single SQL UPDATE statement that only changes the status if it is different, then checks the result before publishing an event. The commit message calls this a 'possible race condition' but does not describe a specific security outcome.

AI review queuedfeat: Add Update button to disabled plugins section (#7260)by rollforsats · 044e0b56 · Mar 25, 2026 · 3 filesMessage 100 · StrongInformational 21Details
Commit message · rollforsats

feat: Add Update button to disabled plugins section (#7260)

* Add Update button to disabled plugins section

When a disabled plugin has a newer version available in the plugin repository, show an Update button in the Disabled Plugins row. This lets users update directly without scrolling to the Available Plugins section.

- Add Update button with pending state ("Marked for update") matching existing Enable/Uninstall patterns
- Fetch all plugins unfiltered once to support update lookups regardless of search filter, with in-memory search filtering
- Extract update-finding logic into testable static method (ListPluginsViewModel.GetDisabledPluginUpdates)
- Add 7 unit tests covering version matching, dependency preference, fallback behavior, null safety, and case-insensitive matching

* Address PR feedback

- Make the disabled-row command lookup case-insensitive
- Optimize available update lookup for disabled plugin, dependencies met check removed in lookup since handled in the UI
- Leaving DependenciesMet check alone in UI for now since the logic is handled the same in other places of the manage plugins page

* Address feedback: Use case-insensitive matching and prioritize newer versions when building the available plugins map.

- availablePluginsByIdentifier will now prefer the newest version when setting the available plugin value in the map
- use case insensitive identifier matching
- tests for changes,

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 21/100

This commit adds an 'Update' button for disabled plugins in BTCPay Server's plugin management page. It lets users update a disabled plugin directly from the disabled-plugins list instead of scrolling to the available-plugins section. The change also fetches all plugins unfiltered once and does search filtering in memory, and adds unit tests. There is no clear security bug in the diff, but the change touches plugin installation commands and identifier matching, which are security-sensitive areas.

Lower-priorityBumping LND to 0.19.3-beta-1 (#7278)by rockstardev · 0e23f916 · Mar 25, 2026 · 4 filesMessage 53 · ThinTriage 0Details
Commit message · rockstardev

Bumping LND to 0.19.3-beta-1 (#7278)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-prioritySubscriptions: SubscriberDisabled webhook now includes the reason why subscriber has been disabled (#7270)by Nicolas Dorier · c25339d6 · Mar 25, 2026 · 7 filesMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Subscriptions: SubscriberDisabled webhook now includes the reason why subscriber has been disabled (#7270)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Security candidatefix(email): skip SMTP AUTH when Login and Password are empty (fixes #7267) (#7269)by Drake Thomsen · 94320733 · Mar 25, 2026 · 1 fileMessage 98 · StrongInformational 22Details
Commit message · Drake Thomsen

fix(email): skip SMTP AUTH when Login and Password are empty (fixes #7267) (#7269)

When SMTP is configured via IP relay (e.g. Google Workspace relay) without
login credentials, BTCPay still calls AuthenticateAsync if the server
advertises AUTH capability, causing 535 errors.

Skip authentication when both Login and Password are empty.

Co-authored-by: Storm Knight <storm-knight@openclaw.ai>

98/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlcredential or privilege state
AI analysis · Informational 22/100

This commit fixes an email-sending bug in BTCPay Server. When an administrator configured an SMTP relay that does not require a username or password, BTCPay was still trying to log in if the server said it supported authentication. That caused unnecessary 535 authentication errors and prevented emails from being sent. The fix simply skips login when both the Login and Password fields are empty. There is no security vulnerability here; it is a reliability/configuration fix.

AI review queuedFix flaky testby Nicolas Dorier · 068670a9 · Mar 25, 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 only changes a test file. It replaces some direct text equality checks with Playwright's built-in 'expect element to contain text' helper, which waits for the text to appear rather than checking instantly. The goal is to make a flaky (sometimes failing) test more stable. There is no change to production code and no security relevance.

Lower-priorityAdd: Implement UpdateCrowdfundApp endpoint and client method (#7202)by SiriusBig · 8e748f9d · Mar 25, 2026 · 4 filesMessage 91 · StrongTriage 8Details
Commit message · SiriusBig

Add: Implement UpdateCrowdfundApp endpoint and client method (#7202)

* Add: Implement UpdateCrowdfundApp endpoint and client method

- Added a new API endpoint to update properties of a Crowdfund app in GreenfieldAppsController.
- Introduced request validation for the update operation, ensuring required fields are checked.
- Updated Swagger documentation to include the new PUT operation for Crowdfund apps.
- Added corresponding client method in BTCPayServerClient for making requests to the new endpoint.

* Enhance: Update ToCrowdfundSettings method to merge request with existing settings

- Modified the ToCrowdfundSettings method to accept existing settings, allowing for selective updates based on non-null properties in the request.
- Updated the call to ToCrowdfundSettings in the app update logic to include the existing settings.

* Refactor: Adjust description handling in Crowdfund app updates

- Updated the logic to preserve the description during partial updates, ensuring it defaults to existing settings only when omitted by the client.
- Modified validation to only reject empty descriptions when explicitly provided, improving compatibility with legacy apps.

* Enhance: Add extra validation for reset-related fields in Crowdfund app updates

- Implemented additional checks when patching reset-related fields without specifying ResetEvery, ensuring a start date is provided and the reset amount is valid.
- Improved error handling to guide users on required fields for effective goal resetting.

* Add Update tests to CanCreateReadUpdateAndDeleteCrowdfundApp

Add Crowdfund PUT tests: full update, partial update, validation

* Fix UpdateCrowdfundApp to behave as a true PUT, not a PATCH

The previous implementation silently ignored missing fields and merged them from the existing app, which is inconsistent with the rest of the API. Users who want to update should GET, modify, then PUT the full
payload.

- Remove merge overload ToCrowdfundSettings(request, existing)
- Always call ValidateAppRequest so AppName is required
- Always overwrite app.Name and app.Archived unconditionally
- Update tests: replace patch-specific cases with proper PUT validation
- Fix swagger description and add missing displayPerksRanking field

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validation
Lower-prioritySubscriptions: Can delete subscribers via UI and API (#7254)by Nicolas Dorier · fa6baded · Mar 24, 2026 · 8 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier

Subscriptions: Can delete subscribers via UI and API (#7254)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body