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 1 hour, 1 minute 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.

Lower-priority(Refactor): Removed Selenium Test for CanAccessUserStoreAsAdminby Abhijay jain · edac1e7e · Nov 13, 2025 · 1 fileMessage 75 · AdequateTriage 0Details
Commit message · Abhijay jain

(Refactor): Removed Selenium Test for CanAccessUserStoreAsAdmin

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 CanAccessUserStoreAsAdminby Abhijay jain · bb7d14f7 · Nov 13, 2025 · 1 fileMessage 75 · AdequateTriage 0Details
Commit message · Abhijay jain

(Test):Converted/Added Playwright Test for CanAccessUserStoreAsAdmin

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-priorityRefactor: Move all email tests to same class EmailTestsby Nicolas Dorier · 955dd635 · Nov 12, 2025 · 7 filesMessage 72 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Refactor: Move all email tests to same class EmailTests

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityRefactor: Add UIExtensionsRegistryby Nicolas Dorier · 52a73d4d · Nov 12, 2025 · 3 filesMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Refactor: Add UIExtensionsRegistry

The component UIExtensionPoint was injecting IEnumerable<IUIExtension>
and then filtering on those.
As the number of IUIExtension grows, this operation grows at O(n).

Now we use UIExtensionsRegistry instead which use lookups. O(1)

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI review queuedRefactor: Move email services to the email plugin directoryby Nicolas Dorier · b6c635c2 · Nov 12, 2025 · 43 filesMessage 62 · AdequateInformational 12Details
Commit message · Nicolas Dorier

Refactor: Move email services to the email plugin directory

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 12/100

This commit is a code reorganization: it moves BTCPay Server's email-sending code from a shared 'Services/Mails' folder into the existing 'Plugins/Emails' plugin directory. File paths and namespace references are updated across the project, but the actual logic for sending email, validating settings, and checking certificates is copied almost unchanged. There is no indication this change fixes or introduces a security vulnerability.

Lower-priorityRemove the store invitation notification to store ownersby Nicolas Dorier · 46156a5a · Nov 11, 2025 · 13 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Remove the store invitation notification to store owners

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityFix: When running more than one test in a test run, only the first would load plugins correctly (#6985)by Nicolas Dorier · 894643c5 · Nov 11, 2025 · 1 fileMessage 100 · StrongTriage 0Details
Commit message · Nicolas Dorier

Fix: When running more than one test in a test run, only the first would load plugins correctly (#6985)

Reported by @napoly.

## Actual behavior

Two tests were created. When we would run the tests through the runner,
ASP.NET wouldn't find the registered view of the plugin.

## Expected behavior

The second test should works find, ASP.NET should properly find the
views of the plugin when there are more than one test in the same test
run.

## Cause

If we detected that a plugin assemly was already in the AppDomain, then
we were not loading the ApplicationParts of such assembly.
This wasn't the case for the first test run, but would be after.

The reason for initially doing this was that long time ago, we would
test plugins by referencing them from BTCPaySevrer project. But since
this is not how we are doing things anymore, I think it is safe to
remove this "Feature".
This feature was broken anyway since we started loading plugins in their
own context, but this wouldn't happen with the old way of referencing
plugins from BTCPayServer. (#6851)

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
Lower-priority(Refactor) : Converted Selenium test for `CanCreateStores` and Others to playwright (#6938)by Abhijay Jain · 2ca06c66 · Nov 11, 2025 · 3 filesMessage 91 · StrongTriage 0Details
Commit message · Abhijay Jain

(Refactor) : Converted Selenium test for `CanCreateStores` and Others to playwright (#6938)

* refactor : resolved merge conflicts

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

* (Refactor): Removed Selenium Test for CanCreateStores

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

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

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

* (Refactor): Removed Selenium Test for CanUseCoinSelection

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

* refactor: resolved merge conflicts

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

* refactor: resolved merge conflicts

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

* refactor : resolved minor issues

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

* refactor : updated tests

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

* refactor: updated test

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

* refactor: addressed requested changes

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

* refactor: addressed requested changes

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

---------

Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
Signed-off-by: Abhijay jain <Abhijay007j@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
AI review queuedAdd CC and BCC to emailsby Nicolas Dorier · dcf60e20 · Nov 10, 2025 · 16 filesMessage 38 · OpaqueLow 25Details
Commit message · Nicolas Dorier

Add CC and BCC to emails

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 · Low 25/100

This commit adds CC and BCC fields to BTCPay Server's email rules and refactors how email addresses are parsed. It is a feature addition, not a clear security fix. The new parsing logic uses a placeholder-replacement trick that could mask malformed addresses, and the validation is only partial, so there is a small chance of misdirected or failed emails. There is no evidence in the commit or supplied references that the vendor is treating this as a security issue.

Lower-priorityFix: Rich TextBox (Summernote) not saving changes in code-viewby Nicolas Dorier · 88d3e7ad · Nov 10, 2025 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · Nicolas Dorier

Fix: Rich TextBox (Summernote) not saving changes in code-view

The richtext box had an annoying bug: If you switch to code view, modify
the code then save, the changes would be ignored.

One had to switch back to preview mode prior to save. (See
summernote/summernote#94 for more details)

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-priorityAdd invite and confirmation emailsby Nicolas Dorier · d7fcd557 · Nov 10, 2025 · 17 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add invite and confirmation emails

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd default server email rules in migrationby Nicolas Dorier · 3948eb13 · Nov 10, 2025 · 18 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add default server email rules in migration

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedAdd Server Email Rulesby Nicolas Dorier · b7aed3e3 · Nov 10, 2025 · 39 filesMessage 28 · OpaqueLow 28Details
Commit message · Nicolas Dorier

Add Server Email Rules

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

This commit refactors BTCPay Server's email handling into a new 'Server Email Rules' plugin. It moves server and store email settings into shared base controllers, adds server-wide email rules (for example password-reset emails), and changes how password-reset emails are generated. The changes are mostly architectural and feature-adding; there is no clear evidence in the diff of a security vulnerability being fixed or introduced. However, the new code does involve email templating, SQL queries, and authorization boundaries, so it warrants normal review rather than being dismissed as purely cosmetic.

Lower-priority(Refactor) : Converted Selenium test for `CanUsePairing` and Others to playwright (#6927)by Abhijay Jain · 999bd4db · Nov 5, 2025 · 3 filesMessage 68 · AdequateTriage 0Details
Commit message · Abhijay Jain

(Refactor) : Converted Selenium test for `CanUsePairing` and Others to playwright (#6927)

68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityDo not save cache of rates in the database (#6978)by Nicolas Dorier · 849b27cf · Nov 5, 2025 · 3 filesMessage 93 · StrongTriage 0Details
Commit message · Nicolas Dorier

Do not save cache of rates in the database (#6978)

We were previously saving the rates in the database in a JSONB blob
column. However, the volume of data ise consequential enough for
provoking timeouts during update.

Due to how postgres works, this also create bloat in the database that
isn't cleaned immediately.

This PR fixes this issue by saving the cache in files instead.

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Lower-priorityRefactor ToggleUser->SetDisabled (#6975)by Nicolas Dorier · 14117452 · Nov 5, 2025 · 3 filesMessage 43 · ThinTriage 0Details
Commit message · Nicolas Dorier

Refactor ToggleUser->SetDisabled (#6975)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityFix: Denied 403 page if denied access to default store (#6976)by Nicolas Dorier · 5a5b0c21 · Nov 5, 2025 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · Nicolas Dorier

Fix: Denied 403 page if denied access to default store (#6976)

If a user go to store A, then lose access to store A, any attempt to
browse the home page will return a 403 error.

The user would then get stuck, unable to select a new store until he
clears the cache.

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: Wallet report were showing negative balance change in green (#6974)by Nicolas Dorier · d53b36c2 · Nov 4, 2025 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Wallet report were showing negative balance change in green (#6974)

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
Security candidateRefactor access to the ViewModel of the MainLayout (#6970)by Nicolas Dorier · 54cec835 · Oct 31, 2025 · 149 filesMessage 58 · ThinInformational 20Details
Commit message · Nicolas Dorier

Refactor access to the ViewModel of the MainLayout (#6970)

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
seed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Informational 20/100

This is a large internal refactoring of how BTCPay Server's web UI tracks which navigation menu item is active. It replaces scattered, string-based helpers with a single LayoutModel and a new Razor tag helper. There is no obvious security vulnerability in the change; it is primarily code cleanup and test updates to match the new HTML IDs.

Lower-priorityDisable cookie access when a user is disabled (#6971)by Nicolas Dorier · b8fcb83f · Oct 30, 2025 · 4 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier

Disable cookie access when a user is disabled (#6971)

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 queued[Features] Subscriptionsby nicolas.dorier · b1cba47a · Oct 28, 2025 · 95 filesMessage 18 · OpaqueLow 27Details
Commit message · nicolas.dorier

[Features] Subscriptions

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 27/100

This is a large feature commit adding a new Subscriptions system to BTCPay Server. It introduces new database tables, models, UI pages, API permissions, webhooks, and business logic for managing subscription plans, subscribers, customer identities, checkouts, and portal sessions. There is no explicit security fix or vulnerability disclosure in the commit message or diff. The change is a feature addition, not a documented security patch.

Security candidateUnify delete confirmation confirm dialog (#6965)by Nicolas Dorier · ff02c0f5 · Oct 26, 2025 · 28 filesMessage 53 · ThinInformational 20Details
Commit message · Nicolas Dorier

Unify delete confirmation confirm dialog (#6965)

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
signing or wallet pathboot or update pathauthentication path
AI analysis · Informational 20/100

This commit standardizes the wording and behavior of delete-confirmation dialogs across the BTCPay Server web interface. Previously, different screens asked users to type different words such as "DELETE" or "REMOVE" to confirm deletion. Now every confirmation prompt uses the same word, "Delete," and the check is case-insensitive. This is a user-experience and consistency improvement, not a fix for a security vulnerability.

Lower-priorityFix: Unable to reset email settings (#6963)by Nicolas Dorier · 42490c38 · Oct 23, 2025 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Unable to reset email settings (#6963)

65/100 · AdequateMessage clarity
✓ 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
Lower-priorityAdding test for unique ReferenceIdby rockstardev · 09b1b895 · Oct 22, 2025 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · rockstardev

Adding test for unique ReferenceId

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityAdding validation of ReferenceId for Payment Requestby rockstardev · aa6944b0 · Oct 22, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · rockstardev

Adding validation of ReferenceId for Payment Request

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body