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 40 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-priorityfix: standardize topbar dropdown menus (#7425)by thgO.O · 36eaf4ae · Jul 7, 2026 · 7 filesMessage 65 · AdequateTriage 0Details
Commit message · thgO.O

fix: standardize topbar dropdown menus (#7425)

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
AI review queuedFix "File traversal detected" crash processing plugin commands on Windows (#7422)by Andrew Camilleri · a8c01be5 · Jul 7, 2026 · 1 fileMessage 58 · ThinLow 33Details
Commit message · Andrew Camilleri

Fix "File traversal detected" crash processing plugin commands on Windows (#7422)

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

This commit fixes a bug in BTCPay Server's plugin system where a safety check that prevents directory traversal attacks was accidentally rejecting valid plugin names on Windows. The original code always appended a '/' slash, but Windows uses '\' as its path separator, so the safety check compared paths with mismatched slashes and falsely flagged them as attacks, causing a crash. The fix makes the trailing slash match the operating system's separator. There is no direct evidence in the commit that an actual security vulnerability was exploited; it appears to be a bug fix for a false-positive crash.

Lower-priorityGreenfield: support includePaymentMethods on get invoice (#7426)by Atharva Borade · 76e089ae · Jul 6, 2026 · 4 filesMessage 58 · ThinTriage 0Details
Commit message · Atharva Borade

Greenfield: support includePaymentMethods on get invoice (#7426)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityFix broken default rate calculation for DASHby Nicolas Dorier · 5e7fbbf7 · Jul 4, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Fix broken default rate calculation for DASH

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priority Greenfield: support payoutMethods array on invoice refund (#7413)by Atharva Borade · d4da8916 · Jul 3, 2026 · 5 filesMessage 58 · ThinTriage 0Details
Commit message · Atharva Borade

Greenfield: support payoutMethods array on invoice refund (#7413)

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 queuedMake test less flakyby Nicolas Dorier · 7cb03bb3 · Jun 30, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Make test less flaky

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

This commit removes Bootstrap tooltip attributes from a few disabled buttons and archive links in the invoice view. It is a test-flakiness fix with no apparent security relevance.

Lower-priorityFix NBXplorer error rendering (#7421)by Michael Rihani · abd94b97 · Jun 30, 2026 · 1 fileMessage 53 · ThinTriage 0Details
Commit message · Michael Rihani

Fix NBXplorer error rendering (#7421)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityFix: Server admin unable to see the store of usersby Nicolas Dorier · 2a131156 · Jun 29, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Server admin unable to see the store of users

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritybind to all interface even outside of the test container (#7410)by napoly · 250fd224 · Jun 29, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · napoly

bind to all interface even outside of the test container (#7410)

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-priorityFix: LNDHub should be supported by default (Fix #7418)by Nicolas Dorier · 51a5d1d3 · Jun 27, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: LNDHub should be supported by default (Fix #7418)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedAdd blog post announcementby Nicolas Dorier · e5c2a4cc · Jun 25, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Add blog post announcement

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

This commit only adds a link to a blog post announcement in the changelog. It contains no code changes, no security fixes, and no functional modifications.

Lower-priorityAdd tether plugin to plugin compat checkby Nicolas Dorier · 50ae4bfc · Jun 25, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add tether plugin to plugin compat check

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedRestore lndhub supportby Nicolas Dorier · cea07e5e · Jun 24, 2026 · 2 filesMessage 28 · OpaqueInformational 16Details
Commit message · Nicolas Dorier

Restore lndhub support

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

This commit reverts a planned removal of LNDHub support by updating a single Lightning library version and editing the changelog. It is a feature restoration, not a security fix. There is no evidence in the commit of any vulnerability, exploit, or security-relevant change.

AI review queuedFix flaky testby Nicolas Dorier · 23219bc9 · Jun 24, 2026 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flaky test

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

This commit fixes a flaky automated test for the global search feature. The JavaScript change makes the search run automatically if a query is already present when the search UI opens, and the test code is simplified to remove a special screenshot-on-failure workaround. There is no security issue here.

Lower-priorityRemove useless SubTitle property to global search vmby Nicolas Dorier · 54521cf4 · Jun 23, 2026 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Remove useless SubTitle property to global search vm

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd entry for dyndns setupby Nicolas Dorier · 2699770c · Jun 23, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add entry for dyndns setup

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityTry to catch flaky GlobalSearch testby Nicolas Dorier · 67cda519 · Jun 23, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Nicolas Dorier

Try to catch flaky GlobalSearch test

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityAdd breaking change notice to changelogby Nicolas Dorier · 6828fc83 · Jun 22, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add breaking change notice to changelog

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityBumping LND to 0.21.0-betaby rockstardev · 307acf4d · Jun 22, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · rockstardev

Bumping LND to 0.21.0-beta

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd support for core lightning 26.06 (#7412)by Nicolas Dorier · 77839370 · Jun 22, 2026 · 6 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add support for core lightning 26.06 (#7412)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedImprove phoenixd, remove support for deprecated lightning backendby Nicolas Dorier · 009f458e · Jun 19, 2026 · 22 filesMessage 50 · ThinInformational 22Details
Commit message · Nicolas Dorier

Improve phoenixd, remove support for deprecated lightning backend

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 22/100

This commit is a routine maintenance update for BTCPay Server. It removes support for three older/deprecated Lightning payment backends (Lightning Charge, LNDHub, and LNBank), updates the phoenixd integration, bumps a couple of library versions, and adjusts tests accordingly. There is no indication in the commit that this fixes an active security vulnerability or introduces new attack paths.

Lower-priorityfix: bulk archive pull payments scoped to current store (#7407)by Atharva Borade · ee2a64c2 · Jun 18, 2026 · 2 filesMessage 93 · StrongTriage 0Details
Commit message · Atharva Borade

fix: bulk archive pull payments scoped to current store (#7407)

MassAction was passing selectedItems to Cancel() without a store filter,
allowing a user with CanArchivePullPayments on store A to archive pull
payments from other stores. Filter PullPaymentIds by StoreIds in
HandleCancel before attaching the archived flag.

Signed-off-by: atharrva01 <adityashinde1525@gmail.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedFix: When a server has too many apps, the Policies page timeout or crash (#7406)by Nicolas Dorier · e6085835 · Jun 17, 2026 · 4 filesMessage 70 · AdequateLow 37Details
Commit message · Nicolas Dorier

Fix: When a server has too many apps, the Policies page timeout or crash (#7406)

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

This commit fixes a performance problem on the BTCPay Server 'Policies' settings page. Previously, the page tried to load a dropdown list of every app on the server, which could time out or crash when there were many apps. The fix replaces the dropdown with a simple text box where the administrator types an app ID directly. It also adds validation to reject invalid app IDs instead of crashing. The change is primarily a reliability/performance fix, but it slightly changes how app IDs are entered and validated.

AI review queuedAdd missing translationsby Nicolas Dorier · ea692b4a · Jun 15, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Add missing translations

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 missing translated text labels for a global search feature. It changes hardcoded English hint text into references to the project's translation system so the hints can appear in other languages. There is no security relevance.

AI review queuedMissing translationby Nicolas Dorier · 64797ee2 · Jun 15, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Missing translation

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: security-sensitive path
AI analysis · Informational 15/100

This commit changes a single user-visible label from a plain English string to a translatable string. It is a routine localization fix with no security relevance.