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 24 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 candidate[Feature] Monetization (#6986)by Nicolas Dorier · bcb5c56b · Dec 2, 2025 · 97 filesMessage 43 · ThinLow 40Details
Commit message · Nicolas Dorier

[Feature] Monetization (#6986)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 40/100

This is a large feature commit titled 'Monetization' that adds subscription and paid-access functionality to BTCPay Server. It introduces new plugins for monetization and subscriptions, changes how user login restrictions are enforced, adds a 'limited login' authentication scheme, and refactors user registration/invitation email flows. The changes touch authentication, authorization, billing, and user lifecycle logic. While the commit is framed as a feature, several areas have security implications: a new limited-login path that signs users in under a separate scheme when normal login is blocked, changes to password-reset and invitation-token handling, and new database entities for plans/subscribers/portal sessions. No explicit security bug is visible in the diff, but the breadth and sensitivity of the modified code means defects could have significant consequences.

Lower-priority(Refactor) : Converted Selenium test for `CanUseRoleManager` and Others to playwright (#6996)by Abhijay Jain · 65dc0a76 · Nov 27, 2025 · 4 filesMessage 96 · StrongTriage 0Details
Commit message · Abhijay Jain

(Refactor) : Converted Selenium test for `CanUseRoleManager` and Others to playwright (#6996)

* refactor: resovled merge conflict

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

* (Refactor): Removed Selenium Test for CanUseRoleManager

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

* Refactor : removed spacing and extra alert message

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

* (Test):Converted/Added Playwright Test for CanSigninWithLoginCode

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

* (Refactor): Removed Selenium Test for CanSigninWithLoginCode

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

* fix: updated UIServerController.Roles.cs to handle storeID

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

* refactor : updated some minor nits

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

* Fix: Preserve store context when deleting server-wide roles from store page

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

* refactor: fix auth mismatch in role Edit/Remove links for store context

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

---------

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

96/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✓ Names security-relevant behavior explicitly
Lower-priorityFix clipboard copy for fiat amounts and other numeric values (#7011)by psam21 · ab6aa1e9 · Nov 27, 2025 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · psam21

Fix clipboard copy for fiat amounts and other numeric values (#7011)

Co-authored-by: rockstardev <5191402+rockstardev@users.noreply.github.com>

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-priorityfeat : add functionality to download language pack (#6943)by Abhijay Jain · 03349b6f · Nov 26, 2025 · 3 filesMessage 81 · StrongTriage 0Details
Commit message · Abhijay Jain

feat : add functionality to download language pack (#6943)

* refactor : added link to translations files

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

* feat : added ability to download langauge pack

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

* refactor: removed link for the edit page

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

* refactor: server-side downloading instead of JavaScript

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

* refactor : addressed request changes

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

* refactor: updated GetDictionary method and other changes

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

---------

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

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedFix property name: use CanUseHotWallet and CanCreateNewColdWalletby psam21 · cf692c6e · Nov 24, 2025 · 1 fileMessage 50 · ThinLow 29Details
Commit message · psam21

Fix property name: use CanUseHotWallet and CanCreateNewColdWallet

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100

This is a tiny one-line fix in a BTCPay Server web page that checks whether a user is allowed to set up certain types of cryptocurrency wallets. The old code referenced two properties that appear to have been renamed or replaced. The change simply swaps in the current property names so the page renders the wallet-setup section correctly. It is most likely a routine bug fix, but because it touches permission checks for wallet creation, it could have security-adjacent effects if the wrong users were shown (or hidden from) wallet options.

Security candidateHide wallet creation option when permissions disabledby psam21 · 09e2b3e7 · Nov 24, 2025 · 2 filesMessage 81 · StrongLow 40Details
Commit message · psam21

Hide wallet creation option when permissions disabled

- Pass wallet creation permissions to SetupWallet view
- Conditionally render 'Create a new wallet' based on CanCreateHotWallet || CanCreateWalletWatchOnly
- Remove 'I have a wallet' and 'I don't have a wallet' section headings
- Always show 'Connect an existing wallet' option (import is always allowed)

Fixes #6991

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege statesigning or wallet path
AI analysis · Low 40/100

This commit fixes a UI bug where BTCPay Server was showing a 'Create a new wallet' button to users who did not have permission to create wallets. The button itself was just a link; the actual wallet creation endpoint still enforced permissions separately. So the fix is about hiding an option that shouldn't appear, not about blocking an unauthorized action. It is a defense-in-depth or user-experience security improvement rather than a critical vulnerability.

Lower-priorityIssue 6918 re enable plugin (#6930)by monicamuyama · 5a487985 · Nov 21, 2025 · 5 filesMessage 76 · AdequateTriage 0Details
Commit message · monicamuyama

Issue 6918 re enable plugin (#6930)

* Added the enable button on disabled plugins

* Added the disable function and button for installed plugins

* Changes based on the coderabbitai comments

* Removed markers and added the disable in the same if block as the unistall

* Hide the uninstall button when plugin is queued for enabling

* Removed the duplicate enale function

* Removed the disable button for installed plugins

* Removed the disableplugin functions as they are no longer needed

* Trigger CI pipeline after dotnet restore

* reverted the git ignore

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedFix missing assignationby Nicolas Dorier · 0a518320 · Nov 21, 2025 · 1 fileMessage 28 · OpaqueLow 34Details
Commit message · Nicolas Dorier

Fix missing assignation

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 34/100

This commit fixes a simple but potentially important coding mistake: a constructor parameter named `loadAssembliesInDefaultLoadContext` was not being saved into its matching field. As a result, the plugin loader's intended setting about where to load assemblies was effectively ignored, and the code would fall back to the default value (false). This could change how plugins are isolated from the main application, potentially weakening the sandbox between plugins and the host.

Lower-priorityTests: All plugin integration tests to resolve plugin's typesby Nicolas Dorier · e002f59f · Nov 21, 2025 · 6 filesMessage 91 · StrongTriage 0Details
Commit message · Nicolas Dorier

Tests: All plugin integration tests to resolve plugin's types

Reported by @napoly

In an integration test for a plugin, attempt to resolve a type provided by that plugin using `BTCPayServerTester`.

For example:
```
tester.GetService<MoneroRPCProvider>();
```

The type should be resolved successfully.

The type fails to resolve.

During the test run, the dotnet runtime attempts to load `MoneroRPCProvider` in the default load context (`AssemblyLoadContext.Default`). It locates the plugin assembly in the test directory and loads it there.

In contrast, when BTCPay Server loads a plugin, it creates a dedicated plugin load context, and the plugin’s `MoneroRPCProvider` is loaded inside that context. This results in two distinct `MoneroRPCProvider` types: one in the default context and one in the plugin context.

This PR forces the plugin context, during integration tests, to load the types it resolves into the default assembly context rather than its own. This prevents duplicate type definitions.

As a side effect, behavior may differ slightly between running BTCPay Server normally and running tests, but this should be acceptable in most cases.

Relevant discussion: #6851

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
AI review queuedFix flacky CanUseFormsby Nicolas Dorier · 4e34a185 · Nov 21, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flacky CanUseForms

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

This commit fixes a flaky automated test, not a security issue. The test previously checked the entire web page content for an email address, which could fail if the email appeared anywhere else on the page or if timing caused the page content to be incomplete. The change narrows the check to look specifically at the value of the email input field. There is no indication this affects real users or production code.

Lower-priorityAdd a 'Pending invoice' pill in portal subscription when invoice processingby Nicolas Dorier · 2f8be8c9 · Nov 19, 2025 · 5 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add a 'Pending invoice' pill in portal subscription when invoice processing

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd buyerEmail to invoice metadata created by suscribersby Nicolas Dorier · 0e649a68 · Nov 19, 2025 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add buyerEmail to invoice metadata created by suscribers

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedImprove testby Nicolas Dorier · 6b76af43 · Nov 18, 2025 · 6 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Improve test

28/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! 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 is a routine test and code-quality improvement. It tightens a test helper that was incorrectly always setting IsAdmin to true, modernizes some C# syntax, removes unused imports, and adds test-id attributes to a web page so automated tests can locate elements more reliably. There is no security-relevant change to production behavior.

Lower-priorityFix: SVG icons stop displaying when served from cache (#7003)by Nicolas Dorier · c97ddd16 · Nov 18, 2025 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · Nicolas Dorier

Fix: SVG icons stop displaying when served from cache (#7003)

See #7003

The fix seems to be to just reinsert the svg into the page once it is
loaded. This is probably a browser bug...

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
AI review queuedRemove LocalBTCPayClientby Nicolas Dorier · ccbc0614 · Nov 18, 2025 · 4 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Remove LocalBTCPayClient

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 removes an internal-only API client called LocalBTCPayClient. It was a convenience wrapper that let server code call BTCPay Server's own Greenfield API without making real HTTP requests. There is no indication this change fixes a security vulnerability; it appears to be a code cleanup or architectural simplification.

Lower-priorityValidate scopes of service injections in testsby Nicolas Dorier · 749c7722 · Nov 15, 2025 · 11 filesMessage 55 · ThinTriage 8Details
Commit message · Nicolas Dorier

Validate scopes of service injections in tests

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validation
Lower-priorityFix: Spurious EF error on CallbackGeneratorby Nicolas Dorier · c9dcd4f0 · Nov 14, 2025 · 10 filesMessage 57 · ThinTriage 0Details
Commit message · Nicolas Dorier

Fix: Spurious EF error on CallbackGenerator

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidateFeature: Plugin can extend whether an account can login or notby Nicolas Dorier · 41f55882 · Nov 14, 2025 · 13 filesMessage 50 · ThinLow 37Details
Commit message · Nicolas Dorier

Feature: Plugin can extend whether an account can login or not

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 37/100

This commit refactors how BTCPay Server decides whether a user is allowed to log in. It replaces a simple built-in check with a new extensible system where plugins can add their own login-blocking rules. The change touches password logins, two-factor/FIDO2/LNURL logins, API key authentication, and basic HTTP authentication. It also fixes a small bug in basic authentication where the password was checked before the user was validated. There is no claim in the commit that this fixes a known security vulnerability, and no CVE or advisory is referenced.

Lower-priorityFix CI: Unsupported repository version 1. Only versions up to 0 are supported.by Nicolas Dorier · a914d798 · Nov 14, 2025 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Fix CI: Unsupported repository version 1. Only versions up to 0 are supported.

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedFix node menu link styleby Nicolas Dorier · 2926dc40 · Nov 14, 2025 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix node menu link style

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This is a one-line user-interface styling fix in the main navigation menu. It adds a missing layout attribute so a menu link is styled consistently with other navigation items. There is no security relevance.

Lower-priorityrefactor : addressed requested changesby Abhijay007 · cc0570f0 · Nov 13, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Abhijay007

refactor : addressed requested changes

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

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Lower-priorityrefactor : addressed requested changesby Abhijay007 · 1bbb9508 · Nov 13, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Abhijay007

refactor : addressed requested changes

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

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Lower-priorityrefactor: updated testby Abhijay007 · f26f42ba · Nov 13, 2025 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Abhijay007

refactor: updated test

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

65/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Lower-priority(Refactor): Removed Selenium Test for CanChangeUserRolesby Abhijay jain · da53f3a5 · Nov 13, 2025 · 1 fileMessage 75 · AdequateTriage 0Details
Commit message · Abhijay jain

(Refactor): Removed Selenium Test for CanChangeUserRoles

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

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Lower-priority(Test):Converted/Added Playwright Test for CanChangeUserRolesby Abhijay jain · 89acda4f · Nov 13, 2025 · 1 fileMessage 75 · AdequateTriage 0Details
Commit message · Abhijay jain

(Test):Converted/Added Playwright Test for CanChangeUserRoles

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

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification