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 27 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.

Lower-priority[Fix] Prevent LabelManager update loop and stabilize Payment Request label test (#7087)by thgO.O · c99ff3a1 · Jan 8, 2026 · 2 filesMessage 83 · StrongTriage 0Details
Commit message · thgO.O

[Fix] Prevent LabelManager update loop and stabilize Payment Request label test (#7087)

* fix: prevent LabelManager label refresh loop

* test: stabilize PaymentRequest label flow

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
AI review queuedAdd norvegian langby Nicolas Dorier · d082ea7c · Jan 7, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Add norvegian lang

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 simply adds 'Norwegian' as a new language option in a dropdown list inside an administrative view. There is no security relevance: no code logic, permissions, data handling, or user input processing changed.

Lower-priorityFix: In monetization, it was impossible to recreate a user with email of a previously deleted user (#7082)by Nicolas Dorier · 881cd370 · Jan 6, 2026 · 3 filesMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: In monetization, it was impossible to recreate a user with email of a previously deleted user (#7082)

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
Lower-priorityFix: Backend translations would sometimes fail to load during startup (#7083)by Nicolas Dorier · d231b799 · Jan 6, 2026 · 5 filesMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Backend translations would sometimes fail to load during startup (#7083)

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 candidatechore(ci): enforce signature verification before Docker builds (#7077)by Abhijay Jain · 49649f5a · Jan 6, 2026 · 3 filesMessage 100 · StrongInformational 15Details
Commit message · Abhijay Jain

chore(ci): enforce signature verification before Docker builds (#7077)

* chore(ci): enforce GPG signature verification before Docker builds

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

* chore(ci): enforce commit signature verification

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

* chore: updated the code

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

---------

Signed-off-by: Abhijay007 <Abhijay007j@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✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validationsigning or wallet path
AI analysis · Informational 15/100

This commit adds a CI safety check that refuses to build Docker images unless the current Git commit has a valid GPG signature. It is a hardening improvement, not a fix for an active vulnerability. There is no indication in the commit or title that it responds to a known security incident.

Lower-priorityFix: Subs plan checkout always showed 'per month' (#7080)by Nicolas Dorier · 9b87929e · Jan 6, 2026 · 3 filesMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Subs plan checkout always showed 'per month' (#7080)

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
Lower-priorityFix: Editing a plan subcription set the Currency back to USD (#7079)by Nicolas Dorier · 47dcc5f9 · Jan 6, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Editing a plan subcription set the Currency back to USD (#7079)

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
Lower-priorityCoderabbit: Disable docstrings in finishing touchesby Nicolas Dorier · 0c1741ed · Jan 4, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Coderabbit: Disable docstrings in finishing touches

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityFix: "Synching" typo to "Syncing" in UI (#7065)by RecRanger · fdfcde2c · Jan 4, 2026 · 2 filesMessage 80 · StrongTriage 0Details
Commit message · RecRanger

Fix: "Synching" typo to "Syncing" in UI (#7065)

* Fix: "Synching" typo to "Syncing" in UI

* Fix: "Synching" typo to "Syncing" in variable name

80/100 · StrongMessage clarity
✓ 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
Lower-priorityInclude UI extension point for pos (#7073)by Chukwuleta Tobechi · 7f581e61 · Jan 4, 2026 · 1 fileMessage 76 · AdequateTriage 0Details
Commit message · Chukwuleta Tobechi

Include UI extension point for pos (#7073)

* Include UI extension point for pos

* Extension point after header

---------

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

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Security candidateFix: Disable zero amount invoices in PoS doesn't show for Keypad (#7071)by Nicolas Dorier · a4034860 · Jan 3, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Nicolas Dorier

Fix: Disable zero amount invoices in PoS doesn't show for Keypad (#7071)

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
Why it was queued
boot or update path
AI analysis · Informational 15/100

This commit is a simple user-interface fix: it moves a checkbox setting ('Disable zero amount invoices') so it appears in the correct section of the Point of Sale settings page. The setting was previously only shown under the 'Keypad' section, but it should be visible for all Point of Sale types. There is no security issue here.

AI review queuedChangelog 2.3.2by Nicolas Dorier · cb10a6cf · Jan 2, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Changelog 2.3.2

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 is a routine version bump and changelog update for BTCPay Server 2.3.2. It does not change any application code, only the version number and release notes. The changelog describes bug fixes and a new feature, but those actual code changes are not present in this diff.

Security candidatePoS: Can disable zero amount invoices (#7066)by Nicolas Dorier · 884a401d · Jan 2, 2026 · 4 filesMessage 53 · ThinLow 32Details
Commit message · Nicolas Dorier

PoS: Can disable zero amount invoices (#7066)

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

This commit adds a new optional setting for BTCPay Server's Point of Sale (PoS) app that lets store owners block invoices with a zero total amount. Previously, a customer could complete a checkout flow that created an invoice worth nothing, which could be used to generate fake or confusing payment records, test transactions, or possibly abuse downstream systems that expect only paid invoices. The change is a defensive feature, not a fix for a known active attack, and it is disabled by default.

Lower-priorityFix: Payment reminders not send to subscribers (#7064)by Nicolas Dorier · 1dad681a · Dec 31, 2025 · 7 filesMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Payment reminders not send to subscribers (#7064)

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
Lower-priorityFix: In the UI, the prefilled email set when creating a new subscriber was ignored (#7059)by Nicolas Dorier · c24aa9d8 · Dec 29, 2025 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: In the UI, the prefilled email set when creating a new subscriber was ignored (#7059)

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
Lower-priorityFix: Subscriptions Mail tab wasn't always warning about unconfigured emailsby Nicolas Dorier · a1d44464 · Dec 29, 2025 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Subscriptions Mail tab wasn't always warning about unconfigured emails

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedRemove confusing propertyby Nicolas Dorier · db0d3cc3 · Dec 29, 2025 · 2 filesMessage 35 · OpaqueInformational 12Details
Commit message · Nicolas Dorier

Remove confusing property

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 12/100

This commit removes an unused or redundant 'Id' property from a checkout view model in the Subscriptions plugin. The property was being set from a plan identifier but appears to have been 'confusing' rather than functional. There is no indication in the commit that this change fixes a security vulnerability.

Lower-priorityFix/qr url mismatch (#7058)by Yemi Harry · 189c65df · Dec 29, 2025 · 3 filesMessage 68 · AdequateTriage 0Details
Commit message · Yemi Harry

Fix/qr url mismatch (#7058)

* add checkout field to view model

* update checkout to use checkoutid

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Lower-priorityFix: Should never show payment method selector if there's only a single payment method, even with pluginsby Nicolas Dorier · 8035d6f4 · Dec 28, 2025 · 3 filesMessage 62 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Should never show payment method selector if there's only a single payment method, even with plugins

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedFix coderabbit warningby Nicolas Dorier · 34b4df0c · Dec 27, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix coderabbit warning

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 removes one configuration line ('auto_resolve_threads: true') from the project's CodeRabbit AI code-review settings file. It does not change any application code, payment logic, authentication, API behavior, or anything users interact with. There is no security relevance.

Lower-priorityRevert "Hide payment method selector for single payment method invoices" (#7056)by Nicolas Dorier · 820e214b · Dec 27, 2025 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Revert "Hide payment method selector for single payment method invoices" (#7056)

This reverts commit 013187c0a5cdbf03b0008870916b1b0380df03d6.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
AI review queuedFix minor typoby Nicolas Dorier · 346e506a · Dec 23, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix minor typo

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 corrects a spelling mistake in the project's changelog, changing 'upgradding' to 'upgrading'. It does not modify any program code, configuration, or documentation that affects how the software runs or behaves.

AI review queuedDisable all plugins when BTCPay Server crash during startup (#7046)by Nicolas Dorier · fa6107ef · Dec 23, 2025 · 3 filesMessage 58 · ThinLow 31Details
Commit message · Nicolas Dorier

Disable all plugins when BTCPay Server crash during startup (#7046)

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 31/100

This commit changes how BTCPay Server handles crashes caused by plugins during startup. Previously, if a plugin caused a crash, the server would try to disable just that one plugin. The new code can disable all plugins when the server cannot tell which specific plugin is at fault, and it also avoids disabling built-in 'system' plugins. This is a reliability and recovery improvement rather than a fix for a remote attack.

AI review queuedbump 2.3.1by Nicolas Dorier · 1c8f8694 · Dec 23, 2025 · 2 filesMessage 0 · OpaqueInformational 21Details
Commit message · Nicolas Dorier

bump 2.3.1

0/100 · OpaqueMessage clarity
! Very short subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 21/100

This commit is a routine version bump from 2.3.0 to 2.3.1 for BTCPay Server, accompanied by a changelog entry. The changelog describes bug fixes for a startup crash loop caused by plugins, lost email settings after an update, and cleanup of monetized subscribers when users are deleted. There are no code changes in this commit that introduce or fix a security vulnerability directly; it is purely a release metadata update.

Lower-priorityFix: Lost server email settings after update to 2.3.0 (Fix #7038) (#7047)by Nicolas Dorier · 58322ccf · Dec 23, 2025 · 3 filesMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Lost server email settings after update to 2.3.0 (Fix #7038) (#7047)

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