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 24 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: create `lnbits-wallet-paylinks` component (#3523)by dni ⚡ · 3f7a1798 · Nov 21, 2025 · 11 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: create `lnbits-wallet-paylinks` component (#3523)

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 frontend code cleanup: it moves the 'stored paylinks' UI section from the main wallet page into a new reusable Vue component called 'lnbits-wallet-paylinks'. There are no visible security changes—no new permissions, no altered API calls, no changes to how data is handled, and no fixes for known vulnerabilities. It is purely a refactoring to make the code more maintainable.

Security candidate[feat] Payment labels (#3537)by Vlad Stan · 7c7a04da · Nov 21, 2025 · 26 filesMessage 43 · ThinInformational 20Details
Commit message · Vlad Stan

[feat] Payment labels (#3537)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 20/100

This commit adds a new 'payment labels' feature to LNbits, allowing users to tag and filter their payments. It also makes a small change so the app's logo is loaded from the local server instead of an external CDN. The changes are mostly routine feature work, but one part of the code uses a LIKE-based search on stored label data that could, in theory, be tricked into matching unintended records if an attacker can control label values. There is no clear evidence this is exploitable as a practical attack, and the commit does not describe itself as a security fix.

AI review queuedchore: getting rid of jinja variable in wallet.html (#3547)by dni ⚡ · 3ccefb70 · Nov 21, 2025 · 7 filesMessage 70 · AdequateInformational 16Details
Commit message · dni ⚡

chore: getting rid of jinja variable in wallet.html (#3547)

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

This commit is a routine cleanup of the wallet page's frontend code. It removes old server-side template variables (Jinja) and replaces them with client-side JavaScript equivalents so the page is rendered more consistently by the browser. There is no obvious security fix or vulnerability being patched.

AI review queuedfeat: move disclaimer from wallet.html into vue component (#3536)by dni ⚡ · 5346ac47 · Nov 21, 2025 · 12 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

feat: move disclaimer from wallet.html into vue component (#3536)

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 frontend refactoring: it moves the legal disclaimer popup from the wallet page into a reusable Vue component. The only functional code change visible in the diff is renaming a local variable reference from `isFiatPriority` to `g.isFiatPriority` so the wallet page reads the setting from the shared global state object. There is no security fix, no new vulnerability, and no change to backend logic or permissions.

AI review queuedchore: remove unused full withdraw (#3544)by dni ⚡ · 9f4ed538 · Nov 21, 2025 · 2 filesMessage 65 · AdequateInformational 15Details
Commit message · dni ⚡

chore: remove unused full withdraw (#3544)

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 simply removes an unused feature called 'full withdraw' or 'drain funds' from the LNbits wallet UI and backend model. There is no security issue visible in the change itself; it is a cleanup that deletes dead code and an associated QR-code menu option.

AI review queuedrefactor: `lnbits-wallet-charts` and clean up paymentFiltering (#3526)by dni ⚡ · faac56c1 · Nov 20, 2025 · 12 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: `lnbits-wallet-charts` and clean up paymentFiltering (#3526)

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 frontend code cleanup. It moves wallet chart rendering into a new reusable component, renames some balance-formatting helpers, and simplifies how payment filters are passed between components. There is no indication of a security fix or vulnerability being addressed.

AI review queuedfix: login screen layout (#3538)by Tiago Vasconcelos · b9a004a5 · Nov 20, 2025 · 11 filesMessage 80 · StrongInformational 15Details
Commit message · Tiago Vasconcelos

fix: login screen layout (#3538)

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

This commit is a UI layout fix for the login screen. It replaces a custom ad banner component with inline HTML and adjusts how ad-space settings are passed from the server to the page. There is no security-relevant change visible in the diff.

AI review queuedrefactor: lnbits-wallet-ads, ads on wallet page (#3534)by dni ⚡ · 41443596 · Nov 17, 2025 · 7 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: lnbits-wallet-ads, ads on wallet page (#3534)

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 frontend refactor that moves the wallet page's advertisement banner from an inline Jinja template into a reusable Vue component. There is no security-relevant change visible in the diff.

AI review queuedrefactor: rename and fix `lnbits-wallet-new` (#3528)by dni ⚡ · f9b5c7db · Nov 14, 2025 · 18 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: rename and fix `lnbits-wallet-new` (#3528)

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 frontend refactor that renames and fixes a wallet-creation UI component. There is no indication of a security vulnerability being patched.

AI review queuedrefactor: move `_wallet-share.html` to vue component (#3522)by dni ⚡ · ff7f5c1c · Nov 13, 2025 · 9 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: move `_wallet-share.html` to vue component (#3522)

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 frontend refactoring: it moves the wallet-sharing user interface from an inline HTML template into a reusable Vue component. There is no change to backend logic, API endpoints, authentication, authorization, or data handling. It is purely a code-organization change in the web UI.

AI review queuedrefactor: move _api_docs.html into vue component (#3520)by dni ⚡ · 1463d75e · Nov 13, 2025 · 12 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: move _api_docs.html into vue component (#3520)

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 straightforward frontend refactoring: it moves the API documentation panel from a server-rendered HTML template into a reusable Vue component. There is no change to how secrets are handled, no new API behavior, and no security fix or vulnerability introduced in the visible code.

AI review queuedrefactor: move `walletTypes` from mixin into `lnbits-new-user-wallet` (#3519)by dni ⚡ · f1fc4710 · Nov 13, 2025 · 5 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: move `walletTypes` from mixin into `lnbits-new-user-wallet` (#3519)

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 code cleanup (refactor) that moves a list of wallet types from a shared mixin file into a specific component for creating new wallets. There is no security-relevant change visible in the diff.

AI review queuedrefactor: use mobileSimple reactive value (#3518)by dni ⚡ · 00eaec82 · Nov 13, 2025 · 12 filesMessage 65 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: use mobileSimple reactive value (#3518)

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 is a routine user-interface cleanup. It moves a mobile-view state flag called mobileSimple into a shared reactive global object (g.mobileSimple) and replaces inline styling with CSS classes. There is no security-relevant change visible in the diff.

AI review queuedrefactor: rename payment-list to lnbits-payment-list (#3517)by dni ⚡ · 28c4235c · Nov 13, 2025 · 8 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: rename payment-list to lnbits-payment-list (#3517)

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 simple rename of a user-interface component from <payment-list> to <lnbits-payment-list>. It only changes component names and file paths in the frontend code; there is no visible change to app behavior and no security fix or vulnerability introduced.

AI review queuedrefactor: create last base.html vue component (#3514)by dni ⚡ · 9d0ec97d · Nov 12, 2025 · 7 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: create last base.html vue component (#3514)

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 frontend refactoring: it moves the last remaining piece of the base HTML template into a reusable Vue component. There is no change to how user data is handled, no new network requests, and no security-sensitive logic added or removed.

AI review queued[feat] user assets (#3504)by Vlad Stan · 39c33699 · Nov 12, 2025 · 28 filesMessage 43 · ThinLow 49Details
Commit message · Vlad Stan

[feat] user assets (#3504)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Low 49/100

This commit introduces a new 'user assets' feature that lets users upload image files to the LNbits server. It replaces an older admin-only image upload feature with a new system where any logged-in user can upload files, subject to size and type limits. The change is a feature addition, not a documented security fix, but it removes a prior file-system upload path and stores files in the database instead. There are some security-relevant design choices worth reviewing, such as whether the MIME-type allow-list and thumbnail generation are robust against malicious uploads.

AI review queuedfix: pay_invoice http error (#3506)by Vlad Stan · 9ffc63b5 · Nov 12, 2025 · 1 fileMessage 65 · AdequateLow 26Details
Commit message · Vlad Stan

fix: pay_invoice http error (#3506)

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

This commit fixes a bug in LNbits' OpenNode wallet integration where failed invoice payments were incorrectly reported as definitively failed (ok=False) instead of uncertain (ok=None), and adds handling for expired invoices. The change makes payment status reporting more accurate, which could prevent users from being incorrectly told a payment failed when it might still be pending or retriable.

AI review queuedrefactor: lndrest get_payment_status and pay_invoice use api v2 (#3470)by dni ⚡ · e038ceb9 · Nov 10, 2025 · 2 filesMessage 85 · StrongLow 34Details
Commit message · dni ⚡

refactor: lndrest get_payment_status and pay_invoice use api v2 (#3470)

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

85/100 · StrongMessage clarity
✓ Specific, 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 34/100

This commit refactors LNbits' LND REST wallet integration to use newer LND API endpoints (v2) for sending payments and tracking payment status. It changes how payment results are parsed and how failures are reported. There is no direct evidence in the commit that this fixes a known security vulnerability; it appears to be a maintenance/API modernization change. However, any change to payment-handling code carries some operational risk.

AI review queuedRevise LNBits Admin UI documentation (#3443)by DoktorShift · b4eccb9e · Nov 10, 2025 · 5 filesMessage 53 · ThinInformational 15Details
Commit message · DoktorShift

Revise LNBits Admin UI documentation (#3443)

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 · Informational 15/100

This commit only updates documentation pages and reorders a dependency in package.json. There are no code changes that affect security, no bug fixes, and no functional changes to the application.

Security candidaterefactor: lndgrpc, update grpcs file, use types and enums, LookupInvoiceV2 (#3469)by dni ⚡ · 691b7ad0 · Nov 10, 2025 · 12 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: lndgrpc, update grpcs file, use types and enums, LookupInvoiceV2 (#3469)

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 pathboot or update path
AI analysis · Informational 15/100

This commit is a routine refactor of the LND gRPC wallet integration in LNbits. It regenerates protocol buffer files from newer LND definitions, adds type stubs (.pyi files), and updates the Python wallet code to use the new LookupInvoiceV2 method and typed enums. There is no indication of a security fix or vulnerability being addressed.

AI review queuedfix: update API response structure and fix checking_id mismatch (#3478)by Sat · c84d1b66 · Nov 10, 2025 · 1 fileMessage 85 · StrongLow 32Details
Commit message · Sat

fix: update API response structure and fix checking_id mismatch (#3478)

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

85/100 · StrongMessage clarity
✓ Specific, 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 32/100

This commit updates LNbits' Strike wallet integration to match a newer Strike API response format and fixes a mismatch in how outgoing payments are tracked. Previously, the code used Strike's internal payment ID as the tracking key ('checking_id'), but now it uses the Lightning invoice's payment hash. The change also adds stricter error handling and fee parsing. The mismatch could have caused LNbits to lose track of whether a payment succeeded, failed, or is still pending, which in turn could lead to double-paying an invoice or incorrectly marking a payment as failed. There is no evidence in the commit of an active security exploit or a CVE.