LN
← All projectsLNbits

LNbits

Self-hosted Lightning wallet, accounts, payment API, and extension platform supporting multiple funding sources.

BitcoinLightning NetworkPayment infrastructureActive incident
Repository coverage

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

51security candidates144second-pass queue196AI analyses
63commits · 30 days
141commits · 60 days
291commits · 180 days
547commits · 365 days
Backfill bands
Nov 8 → May 12291 seen16 candidatesComplete
May 12 → Sep 9146 seen12 candidatesComplete
Sep 9 → Oct 932 seen6 candidatesComplete
Oct 9 → Nov 899 seen10 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.

71/100 average clarity
171Strong · 80–100
341Adequate · 60–79
80Thin · 40–59
6Opaque · 0–39
2security 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.
Vlad Stan1372758564
Arc631127366
Riccardo Balbo403140
dni ⚡185558069
Tiago Vasconcelos38311068
monasco622053
Bitkarrot624085
satcat21111075
dependabot[bot]6400093
blackcoffeexbt1005065
Nathan Day904086
Bartok802081
Analysis record

Published AI watches

Last scanned 10 minutes ago

Low 41 AI analysisMessage 73 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat (wasm): Adds csv/print to wasm iframes, core theme passing, optional unhashed description, scoped invoice status, fiat checkout and browser storage (#4328)

This commit adds several new features to LNbits' WebAssembly (WASM) extension system. It introduces ways for extensions to: check invoice status, refresh payment status, create fiat checkout invoices, store small amounts of data in the bro…

Untrusted `extension_context` dictionary replaced by frozen typed model `PaymentExtensionContext` with required `extension_id`, `owner_id`, `wallet_id`, and optional `source_id`.New `wallet.invoice_status` method enforces strict binding checks (extension, owner, wallet, source) before returning only `paid/pending/failed/amount-msat`; rejects legacy/unbound invoices.New `wallet.refresh_payment` requires authentication, wallet ownership or shared-wallet VIEW_PAYMENTS permission, and scopes payment lookup by wallet; hides backend error details.
df3a180aby Arc+1919−8322 files
No security note in commit
Moderate 63 AI analysisMessage 58 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix[8c7f]: reject SSO for accounts with passwords (#4347)

This update blocks users from logging into password-protected accounts through single sign-on (SSO), such as 'Login with GitHub'. Before this change, an attacker who knew or guessed a victim's email address could potentially use an SSO pro…

Authentication bypass mitigation: SSO can no longer authenticate accounts that also have local passwordsAccount takeover risk reduction: blocks an external identity provider from overriding a password-protected accountState preservation: password hash and email_verified flag remain unchanged on rejection
b1d22089by Vlad Stan+70−23 files
No security note in commit
Low 44 AI analysisMessage 58 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix[8c7f]: keep unrecorded Core Lightning payments pending (#4345)

This commit changes how LNbits interprets a missing Core Lightning payment record. Previously, if no payment record existed, LNbits marked the payment as failed. Now it marks it as still pending, because a payment that is currently being s…

Change in payment state machine: empty result now treated as pending rather than failedPotential race condition between payment initiation and status pollingRisk of duplicate payment attempts if pending status leads to retries
49755d33by Vlad Stan+2−21 file
No security note in commit
High 81 AI analysisMessage 75 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: reject user ID authentication for password accounts (#4340)

This commit fixes an authentication bypass in LNbits. Previously, an account that had been created without a password could still be logged into using only the user ID even after a password was later added. An attacker who knew (or guessed…

Authentication bypass via user ID for password-protected accountsStale authentication cache could grant access after password upgradeNew guard `check_passwordless_account` enforces password requirement
db9563d2by Vlad Stan+196−448 files
Vendor flagged security relevance
Moderate 67 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: respect shared wallet permissions for payment updates (#4338)

This commit fixes a permission bug in LNbits where users of shared wallets could update or settle/cancel payments even when they only had view-only access. It also adds a check so that settle/cancel actions only work on special 'hold invoi…

Access-control bypass fix for shared wallet payment updatesNew permission check can_update_payments() tied to shared wallet receive/send permissionsNew hold_invoice guard on settle/cancel endpoints
d718f9aeby Vlad Stan+154−64 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

chore: remove extension builder from core (#4331)

This commit completely removes the 'Extension Builder' feature from LNbits core. It deletes the backend code that generated extensions from templates, the API endpoints, the web UI pages, and related settings. There is no bug being fixed a…

Removal of a code-generation feature that used Jinja2 with autoescape=False (bandit S701 was previously suppressed for this file)Removal of an endpoint that allowed admins to build, deploy, and activate extensions from user-supplied JSON configurationReduction of extension installation attack surface by removing the builder manifest source and preview file-serving route
c8d47013by Vlad Stan+14−334535 files
No security note in commit
Low 49 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: disable paid reviews (#4325)

This update turns off a default paid-extension review service in LNbits. It stops the wallet from automatically contacting a third-party payment/review server when it lists or updates extensions, and resets the default review URL to empty.…

Default third-party review/payment URL removedMigration forcibly resets stored review URL to emptyBackground extension update/install no longer queries remote pay_link for pricing
77cc2276by Vlad Stan+208−1313 files
No security note in commit
Moderate 60 AI analysisMessage 55 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: packaging/builds (#4319)

This commit fixes a packaging/build issue in LNbits, but the code changes also harden how sensitive funding-source settings (wallet seeds, API keys, macaroons) are exposed and edited through the admin web interface. Previously, non-super a…

Authorization boundary tightened: funding-source credentials restricted to superuser in API and UISeed-integrity check added: configured mnemonic must match persisted seed.dat before settings are writtenBackup confirmation reset when funding seed changes, preventing silent wallet substitution
fe2b0a98by Arc+913−6918 files
No security note in commit
Critical 100 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: Add superuser action to reset all wallet keys (#4320)

This commit adds a recovery feature that lets the LNbits superuser instantly replace every wallet's secret keys, including keys for deleted wallets, and clear any cached copies of the old keys. The vendor says this is needed because of a r…

Vendor describes the change as a recovery control for a security incident involving exposed wallet credentialsVendor states all versions before 1.7.0 are affected and funds are at risk of theftNew superuser-only endpoint can rotate every wallet's admin and invoice keys, including deleted wallets
45a25b24by Vlad Stan+523−58 files
Vendor flagged security relevance
Moderate 63 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: Automatically update extensions on startup and on a schedule (#4314)

This commit adds an automatic extension update feature to LNbits. By default, it checks for and installs newer versions of installed extensions when the server starts, and can repeat that check every 24 hours. Because extensions are downlo…

Automatic download and execution of third-party code is enabled by defaultUpdate source is the extension's configured source_repo, not a vendor-curated storeNo code signature or hash verification is visible in the diff beyond existing archive validation helpers
a16d7752by Vlad Stan+836−1511 files
No security note in commit
Critical 89 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: harden SSRF checks and use explicit local LNURL route opt-ins (#4313)

This commit is a security hardening patch for LNbits, a Bitcoin Lightning wallet platform. It fixes weaknesses in the server's outgoing web-request protections (SSRF, or Server-Side Request Forgery) that could let an attacker trick the LNb…

SSRF hardening: multicast, IPv6 transition/embedded addresses, and EC2 IPv6 metadata endpoint blockedLocal LNURL routing moved from hard-coded regex allow-list to explicit per-route openapi_extra opt-inBackslash path traversal blocked in private HTTP endpoint checks
fc5e0b60by Arc+168−408 files
Vendor flagged security relevance
Critical 90 AI analysisMessage 85 · Strong
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: centralize SSRF protection and block self-targeted requests (#4310)

This is a major security patch for LNbits released after a November incident. It fixes two broad weaknesses: attackers could trick the server into making requests to itself or to internal/cloud services (SSRF), and new user accounts could …

New centralized SafeHttpClient with DNS pinning, redirect limits, and destination validationNew outbound.py blocks requests to the instance hostname and locally assigned/supplied IP addressesSSRF protection applied to LNURL, NIP-05, webhooks, WASM extension HTTP, and WebSockets
7a176c59by Arc+2076−30332 files
Vendor flagged security relevance
Low 35 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix(corelightningrest): compute payment status fee as sent minus amount (#4300)

This commit fixes a bug in how LNbits calculates the fee for a completed Core Lightning REST payment. The old code incorrectly subtracted a negative 'amount sent' value, which produced the wrong fee. The fix changes the formula so the fee …

Incorrect arithmetic in financial/fee calculationTest fixture updated to match corrected sign conventionWallet backend payment status logic changed
45a8704fby Amartya Vikram Singh+2−22 files
No security note in commit
Moderate 52 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: ignore failed payments in daily withdraw limit (#4297)

This commit fixes a bug in LNbits where failed outgoing payments were incorrectly counted against a wallet's daily withdrawal limit. Because failed payments never actually moved money out of the wallet, counting them could wrongly block le…

Business-logic flaw in access-control / spending limitIncorrect state filter on financial transaction queryDenial-of-service-like effect: legitimate withdrawals blocked by stale failed payment records
206477d4by Amartya Vikram Singh+54−02 files
No security note in commit
Low 34 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix(lnpay): return checking_id from create_invoice (#4295)

This commit fixes a bug in the LNPay wallet integration where newly created Lightning invoices were not returning their internal tracking ID ('checking_id'). Without this ID, LNbits could not reliably match future payment updates to the co…

Missing correlation identifier in payment responsePotential invoice state desynchronization between LNbits and LNPay backendRegression test added for payment identifier handling
918b38dcby Amartya Vikram Singh+22−02 files
No security note in commit
Moderate 60 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: prevent duplicate BOLT12 offer payments on retry (#4287)

This commit fixes a bug where retrying a BOLT12 offer payment could accidentally pay the same offer twice. It adds an idempotency check using an external_id so that retries return the original payment instead of creating a duplicate, while…

Duplicate payment prevention for BOLT12 offersIdempotency keyed on wallet_id + external_idConflict detection when external_id reused with different payment details
ea2686d1by Vlad Stan+426−89 files
No security note in commit
High 79 AI analysisMessage 55 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: mempool urls (#4286)

This commit fixes a security gap in LNbits' on-chain (Bitcoin) wallet feature. Previously, a wallet owner could point their wallet at any Mempool-style block explorer URL, including internal or attacker-controlled addresses. The server wou…

Server-Side Request Forgery (SSRF) mitigation: unapproved mempool endpoints are rejected before httpx.AsyncClient is instantiatedOpen redirect / redirect-to-attacker mitigation: follow_redirects=False on mempool requestsInput validation: Pydantic validator strips paths, rejects credentials, fragments, query strings, control chars, backslashes, and invalid ports
f9dd17f3by Vlad Stan+354−2212 files
Vendor flagged security relevance
Low 45 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: payment ws notifications (#4282)

This commit fixes how LNbits notifies the user interface about incoming Lightning payments. Previously, the same paid invoice could be processed and announced multiple times, causing duplicate or confusing wallet notifications. The change …

Race condition in payment status update between polling loop and paid-invoice streamDuplicate WebSocket notifications for the same settled invoiceRefactoring to atomic DB-lock guarded update of incoming payment status
aa041306by Vlad Stan+388−297 files
No security note in commit
Low 39 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

chore: bump to pydantic 2 (#4253)

This is a large dependency upgrade from Pydantic 1 to Pydantic 2 across the LNbits project. Most changes are mechanical renames (e.g., dict() to model_dump(), parse_obj() to model_validate()). A few small functional changes are mixed in: i…

Dependency major-version upgrade (Pydantic 1 -> 2) with broad validation behavior changesRemoval of Pydantic v1 duplicate-validator cache workaround in extension route registrationJWT account resolution reordered to prefer 'usr' claim over 'sub' claim
2ab7662eby Vlad Stan+1548−753119 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: make onchain dialog more readeable (#4269)

This commit is a user-interface redesign of the on-chain Bitcoin receive dialog. It splits the dialog into two screens: one to enter an amount and note, and another to display the QR code. The changes are purely cosmetic and do not alter h…

0e0ee6edby Tiago Vasconcelos+144−804 files
No security note in commit
Repository ledger

Explore captured commits

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

AI review queuedrefactor: `g.settings` with a `PublicSettings` class for mapping, for reactive `WINDOW_SETTINGS` (#3644)by dni ⚡ · 15f093c1 · Feb 25, 2026 · 25 filesMessage 70 · AdequateLow 34Details
Commit message · dni ⚡

refactor: `g.settings` with a `PublicSettings` class for mapping, for reactive `WINDOW_SETTINGS` (#3644)

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
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 34/100

This commit refactors how LNbits exposes site settings to the web frontend. It replaces a hand-maintained list of template variables with a new PublicSettings class that is explicitly marked as safe to expose publicly. The change is mostly a cleanup, but it also slightly alters what information is shown to visitors and how extensions can access it. There is no direct evidence in the commit of a security vulnerability being fixed or introduced, but the refactor touches a sensitive boundary between private server configuration and public web pages.

AI review queuedfeat: wallet featured button (#3740)by Vlad Stan · 5311b0a3 · Feb 25, 2026 · 6 filesMessage 65 · AdequateInformational 15Details
Commit message · Vlad Stan

feat: wallet featured button (#3740)

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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds a new optional 'featured button' to the LNbits wallet page. Administrators can configure a custom label, icon, and URL that appears as a button in the wallet interface. It is a straightforward user-interface customization feature with no security-relevant code changes.

Security candidate[feat] persist user ui customization (#3743)by Vlad Stan · e72396fe · Feb 25, 2026 · 16 filesMessage 53 · ThinInformational 18Details
Commit message · Vlad Stan

[feat] persist user ui customization (#3743)

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
authentication path
AI analysis · Informational 18/100

This commit adds a feature to save a user's visual preferences (theme, language, etc.) on the server so they persist across devices. It introduces a new authenticated API endpoint that stores a JSON blob in the user's account record. The change is a feature addition, not a security fix, and the main risk is that the endpoint accepts arbitrary JSON and merges it into the account with only a size limit for protection.

Security candidate[feat] admin impersonate user (#3741)by Vlad Stan · 9be894da · Feb 25, 2026 · 13 filesMessage 53 · ThinModerate 63Details
Commit message · Vlad Stan

[feat] admin impersonate user (#3741)

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
authentication path
AI analysis · Moderate 63/100

This commit adds an 'admin impersonate user' feature to LNbits. It allows an administrator to log in as another non-admin user by providing that user's ID. The feature is gated behind admin checks and stores the admin's original token in a separate cookie so the admin can later stop impersonating and return to their own session. The change is a deliberate feature, not a hidden backdoor, but it does expand what an admin account can do and could be abused if an admin's session is compromised.

Security candidatefix: better validation error messages (#3736)by Vlad Stan · 67bb86c1 · Feb 25, 2026 · 5 filesMessage 65 · AdequateInformational 19Details
Commit message · Vlad Stan

fix: better validation error messages (#3736)

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
Why it was queued
authentication path
AI analysis · Informational 19/100

This commit changes how LNbits reports validation errors to users. Previously, the API returned a plain string summary of the error. Now it returns a structured list of individual validation failures. This is a user-experience improvement that makes error messages clearer, but it does not fix a security vulnerability and does not introduce a clear one. The main side effect is that error responses now expose slightly more internal detail about which fields failed validation and why.

AI review queuedchore: remove windowMixin from components and pages (#3632)by dni ⚡ · f0f9e41f · Feb 25, 2026 · 49 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

chore: remove windowMixin from components and pages (#3632)

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
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine cleanup that removes the use of a shared 'windowMixin' from many Vue components and pages. It is a refactoring change with no visible security implications.

AI review queuedfix: delete user with wallets (#3711)by Vlad Stan · 5b293767 · Jan 8, 2026 · 3 filesMessage 65 · AdequateLow 28Details
Commit message · Vlad Stan

fix: delete user with wallets (#3711)

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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 28/100

This commit changes how LNbits deletes user accounts. Previously, an admin could not delete a user who still had wallets. Now, deleting a user also deletes all of that user's wallets automatically. The change also centralizes cache cleanup when wallets are removed. There is no direct evidence in the commit that this fixes an active security vulnerability, but it removes a restriction that could have led to leftover wallet data or access credentials when accounts are removed.

AI review queuedfix: password reset from UI (#3712)by Vlad Stan · 957d9ce4 · Jan 8, 2026 · 3 filesMessage 65 · AdequateLow 32Details
Commit message · Vlad Stan

fix: password reset from UI (#3712)

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
Why it was queued
second-pass: broader security terminology
AI analysis · Low 32/100

This commit fixes a bug in LNbits where users could not reset their password through the web user interface. The change is in the frontend JavaScript/Vue code that handles the password reset form. The diff itself is small (+4 -3), but the bundled/minified JavaScript file is also regenerated, making the exact change hard to read. There is no direct evidence in the commit message or diff of a security vulnerability such as account takeover or password reset abuse; it appears to be a functional bug fix for a broken UI flow.

AI review queuedfix(lndrest): use boolean for allow_self_payment instead of integer (#3700)by PatMulligan · 0e21b77b · Jan 8, 2026 · 1 fileMessage 70 · AdequateLow 29Details
Commit message · PatMulligan

fix(lndrest): use boolean for allow_self_payment instead of integer (#3700)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100

This commit fixes a small data-type bug in LNbits' integration with the LND lightning node. The code was sending the number 1 where LND expects a true/false boolean for the 'allow_self_payment' option. Depending on how strictly LND validates the request, this could cause self-payments to be rejected or handled incorrectly, potentially breaking a feature or creating inconsistent payment behavior.

AI review queuedfix: export qrcode was undefined (#3689)by dni ⚡ · bc554748 · Dec 29, 2025 · 3 filesMessage 65 · AdequateInformational 18Details
Commit message · dni ⚡

fix: export qrcode was undefined (#3689)

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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit fixes a JavaScript bug where a QR code export function was called on an undefined object. The change is in the frontend wallet component and only affects the user interface for downloading/exporting a QR code image. It is a routine UI bug fix with no clear security impact.

AI review queuedtest: add boltz fundingsource to regtest (#3677)by dni ⚡ · 132192bc · Dec 22, 2025 · 10 filesMessage 90 · StrongInformational 17Details
Commit message · dni ⚡

test: add boltz fundingsource to regtest (#3677)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit is primarily a test infrastructure change that adds support for a new Bitcoin/Lightning funding source called Boltz to the project's automated regtest test suite. It also includes a small production code change in the payment status API and several bug fixes in the Boltz wallet implementation. The changes look like normal development fixes rather than a security patch. There is no vendor statement or external report indicating this commit fixes a security vulnerability.

AI review queuedfix: Boltzclient fundingsource. use a hashed wallet_name (#3673)by dni ⚡ · a0f65f4c · Dec 17, 2025 · 5 filesMessage 70 · AdequateLow 46Details
Commit message · dni ⚡

fix: Boltzclient fundingsource. use a hashed wallet_name (#3673)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 46/100

This commit changes how LNbits connects to the Boltz funding source. Previously, the Boltz wallet name was a fixed, configurable value (defaulting to 'lnbits'), which could potentially be predictable or leak information. Now, the wallet name is automatically derived as a hash of the LNbits wallet identifier. This makes the name less predictable and reduces the chance that different LNbits instances or wallets collide or are easily guessed. The change is defensive: it removes the explicit 'boltz_client_wallet' setting and updates the backend code and admin UI to reflect the new hashed name behavior.

AI review queuedfeat: Adds paypal as a fiat choice (#3637)by Arc · baee90da · Dec 9, 2025 · 13 filesMessage 80 · StrongLow 37Details
Commit message · Arc

feat: Adds paypal as a fiat choice (#3637)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 37/100

This commit adds PayPal as a new fiat payment option to LNbits, a Bitcoin Lightning wallet platform. It introduces code that lets users create PayPal orders and subscriptions, and receive webhook notifications when PayPal payments complete. The change is a feature addition, not a documented security fix. There are some code-quality concerns in how PayPal webhooks are verified and how subscription metadata is handled, but nothing in the commit or supplied references proves these are exploitable vulnerabilities.

AI review queuedfix: currencies in receive dialog (#3646)by dni ⚡ · 77a5d7fe · Dec 9, 2025 · 2 filesMessage 65 · AdequateInformational 16Details
Commit message · dni ⚡

fix: currencies in receive dialog (#3646)

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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 16/100

This commit is a small UI bug fix for the 'receive' dialog in LNbits. It changes how the list of currencies is populated in the dialog, likely fixing a display issue where fiat currencies were missing or incorrectly shown. There is no clear security problem in the change itself.

AI review queuedFix: Add a QR and Copy button (#3640)by Tiago Vasconcelos · b7fdf99a · Dec 8, 2025 · 3 filesMessage 80 · StrongInformational 16Details
Commit message · Tiago Vasconcelos

Fix: Add a QR and Copy button (#3640)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 16/100

This commit adds a QR code display and a copy-to-clipboard button to the wallet API documentation component in the LNbits web interface. It is a small user-experience improvement for viewing and copying API credentials, not a server-side security fix. There is no indication in the commit that it resolves a vulnerability or that the vendor treats it as a security patch.

AI review queuedfeat: improve on create wallet frontend and api. (BREAKING CHANGE) (#3635)by dni ⚡ · 5f86627e · Dec 8, 2025 · 13 filesMessage 70 · AdequateLow 44Details
Commit message · dni ⚡

feat: improve on create wallet frontend and api. (BREAKING CHANGE) (#3635)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 44/100

This commit changes how wallets are created through the LNbits API. Previously, creating a wallet required an admin key from an existing wallet. After this change, it only requires proof that an account exists. This is a deliberate redesign, but it removes an authorization layer: anyone who can present a valid account identifier can now create a new wallet for that account, whereas before they also needed an existing wallet's admin key. The commit does not explain why this is safe or what replaces the old check, so it may weaken access controls.

AI review queuedfix: typo in walletShareInvoice (#3597)by dni ⚡ · fcaeb0ac · Dec 6, 2025 · 2 filesMessage 65 · AdequateInformational 15Details
Commit message · dni ⚡

fix: typo in walletShareInvoice (#3597)

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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit fixes a simple typo in a wallet-sharing user-interface component. It changes a misspelled property name from 'unsername' to 'username' in the JavaScript source and the matching minified bundle. There is no indication this typo created a security vulnerability; it would most likely have caused the invite form to fail or behave incorrectly.

AI review queuedfix: websocket only listen to filtered wallets (#3627)by dni ⚡ · d2aedde2 · Dec 6, 2025 · 5 filesMessage 70 · AdequateLow 49Details
Commit message · dni ⚡

fix: websocket only listen to filtered wallets (#3627)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 49/100

This commit changes how the LNbits wallet management list listens to WebSocket updates. The title says it now only listens to 'filtered wallets,' which suggests the previous code may have subscribed to updates for all wallets (or a broader set) and could have leaked payment/balance events across wallets visible in the admin or user interface. The actual diff is mostly minified JavaScript bundles, making it hard to verify the exact scope, but the change is consistent with a client-side information-disclosure fix.

AI review queuedfix: deleting the wallet did not update lastActiveWallet (#3628)by dni ⚡ · 71e0b396 · Dec 6, 2025 · 4 filesMessage 70 · AdequateLow 27Details
Commit message · dni ⚡

fix: deleting the wallet did not update lastActiveWallet (#3628)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 27/100

This commit fixes a UI bug where deleting a wallet did not update the user's 'last active wallet' setting in the browser. After deletion, the app could try to load a wallet that no longer exists, causing confusion or a broken wallet view. The fix clears the stored last-active wallet and switches to another available wallet when one is deleted.

AI review queuedfeat: improve on `lnbits-qrcode-scanner` design (#3633)by dni ⚡ · aed3f3b5 · Dec 6, 2025 · 8 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

feat: improve on `lnbits-qrcode-scanner` design (#3633)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine user-interface design improvement for the QR code scanner component in LNbits. It changes how the scanner looks and behaves in the browser, with no apparent security implications. There is no indication it fixes a vulnerability or introduces a security weakness.

AI review queuedfeat: add right arrow for drawer active menu items (#3631)by dni ⚡ · d9a2a7bb · Dec 6, 2025 · 2 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

feat: add right arrow for drawer active menu items (#3631)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a purely cosmetic user-interface change. It adds small right-facing arrow icons next to currently selected menu items in the LNbits web app so users can more easily see which page they are on. There is no security relevance.

AI review queuedfix: exchange rate was not shown on wallet page when switching wallets (#3634)by dni ⚡ · 62047ea7 · Dec 6, 2025 · 3 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

fix: exchange rate was not shown on wallet page when switching wallets (#3634)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit fixes a minor user-interface bug where the exchange rate was not displayed on the wallet page after switching wallets. It is a cosmetic/functional UI fix with no security relevance.

AI review queued[perf] Faster require invoice key (#3603)by Vlad Stan · 850087a8 · Dec 5, 2025 · 14 filesMessage 53 · ThinLow 31Details
Commit message · Vlad Stan

[perf] Faster require invoice key (#3603)

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 pathsecond-pass: security-sensitive path
AI analysis · Low 31/100

This commit is a performance optimization for LNbits, a Bitcoin Lightning wallet platform. It introduces a faster way to check API keys by using a lighter database query and adding caching. The changes mostly refactor existing authentication code rather than fix a clear security bug. There is no explicit security disclosure or advisory associated with this commit.

Security candidateperf: use `check_account_exists` decorator (#3600)by Vlad Stan · b3efb4d3 · Dec 4, 2025 · 12 filesMessage 70 · AdequateLow 34Details
Commit message · Vlad Stan

perf: use `check_account_exists` decorator (#3600)

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
signing or wallet pathauthentication path
AI analysis · Low 34/100

This commit is a performance refactor that replaces a heavier 'check the full user object' dependency with a lighter 'check the account exists' dependency across many API endpoints. It also adds a short-lived cache for authentication lookups. The change is not described as a security fix, but it does touch access-control code, so it needs careful review. There is no direct evidence in the commit of a vulnerability being introduced or fixed.

AI review queuedfeat: update npm packages use terser to minify (#3614)by dni ⚡ · 5213508d · Dec 4, 2025 · 21 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

feat: update npm packages use terser to minify (#3614)

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: unusually broad change
AI analysis · Informational 15/100

This commit is a routine frontend maintenance change: it updates JavaScript/CSS library versions, switches the build minifier to Terser, and refreshes generated bundle files. There is no indication of a security fix, vulnerability, or malicious change in the supplied diff.