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 33 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 queuedfeat(funding): expose allow_self_payment for LND gRPC wallet (#4080)by Vlad Stan · 91c8aa77 · Jul 21, 2026 · 4 filesMessage 85 · StrongLow 27Details
Commit message · Vlad Stan

feat(funding): expose allow_self_payment for LND gRPC wallet (#4080)

Co-authored-by: ai-chen2050 <1033467071@qq.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 27/100

This commit adds a new admin-configurable option called 'allow_self_payment' for the LND gRPC wallet backend in LNbits. When enabled, LNbits will tell the connected LND node to permit payments that start and end at the same node. By default it is turned off. This is a feature addition, not a bug fix, and the commit message and diff do not describe any security vulnerability.

Lower-priorityfix: auto-create new labels in user account via payments API (#4003)by volrabp · 368d0f54 · Jul 21, 2026 · 2 filesMessage 70 · AdequateTriage 0Details
Commit message · volrabp

fix: auto-create new labels in user account via payments API (#4003)

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 queuedfeat: Bark backend support (using barkd) (#4007)by Pavol Rusnak · afa7e1a2 · Jul 21, 2026 · 9 filesMessage 88 · StrongInformational 16Details
Commit message · Pavol Rusnak

feat: Bark backend support (using barkd) (#4007)

Co-authored-by: blackcoffeexbt <87530449+blackcoffeexbt@users.noreply.github.com>
Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

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

This commit adds a new optional wallet backend called BarkWallet to LNbits, allowing LNbits administrators to connect their instance to an external Bark/barkd service. It is a feature addition, not a security patch. There is no direct evidence in the commit that it fixes a known vulnerability or introduces an obvious one. The main security-relevant concern is that the new backend stores an API token in configuration and communicates over HTTP by default, which could leak credentials if the Bark daemon is not on the same trusted local network. The change is opt-in and only affects deployments that explicitly enable BarkWallet.

Lower-priorityi18n: add Faroese (fo) localization (#4067)by krvi · 653924a6 · Jul 21, 2026 · 6 filesMessage 68 · AdequateTriage 0Details
Commit message · krvi

i18n: add Faroese (fo) localization (#4067)

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

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Lower-prioritydocs(guide): fix broken Additional Guides links on funding sources table (#4079)by Bartok · 39e123d3 · Jul 21, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Bartok

docs(guide): fix broken Additional Guides links on funding sources table (#4079)

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
documentation-only discount
Lower-prioritychore(deps): bump axios from 1.16.0 to 1.18.0 (#4075)by dependabot[bot] · d07088cc · Jul 21, 2026 · 4 filesMessage 93 · StrongTriage 0Details
Commit message · dependabot[bot]

chore(deps): bump axios from 1.16.0 to 1.18.0 (#4075)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: alan <alan@lnbits.com>
Co-authored-by: Vlad Stan <stan.v.vlad@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
Why it was queued
automated dependency-update discount
Security candidatefeat: display expiration for ACL tokens (#4033)by Tiago Vasconcelos · 20115b42 · Jul 21, 2026 · 8 filesMessage 80 · StrongInformational 19Details
Commit message · Tiago Vasconcelos

feat: display expiration for ACL tokens (#4033)

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

This commit is a small user-interface feature: it adds an 'expires at' timestamp to API access-control tokens so users can see when each token will expire. The backend now stores the expiration time when a token is created, and the account page displays it. There is no obvious security vulnerability in the change itself; it is purely informational.

Lower-priorityaudio, fullscreen, cursor (#4078)by Arc · 4326888a · Jul 21, 2026 · 3 filesMessage 43 · ThinTriage 0Details
Commit message · Arc

audio, fullscreen, cursor (#4078)

Co-authored-by: alan <alan@lnbits.com>

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-prioritydocs(guide): fix typo enviroment → environment in super user guide (#4073)by Bartok · 9431cef7 · Jul 21, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Bartok

docs(guide): fix typo enviroment → environment in super user guide (#4073)

Co-authored-by: Sera (Bartok9) <sera@local>

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
documentation-only discount
Lower-priorityfeat: add wasm to open api docs (#4074)by Vlad Stan · c5b5651d · Jul 21, 2026 · 16 filesMessage 65 · AdequateTriage 0Details
Commit message · Vlad Stan

feat: add wasm to open api docs (#4074)

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 queuedfeat: add extra warning for admin keys (#4063)by Tiago Vasconcelos · 9177e226 · Jul 21, 2026 · 21 filesMessage 80 · StrongInformational 18Details
Commit message · Tiago Vasconcelos

feat: add extra warning for admin keys (#4063)

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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit adds an extra user-facing warning in the wallet API documentation component to caution users about the sensitivity of admin keys. It is a UI/UX hardening change, not a fix for an active security flaw. The warning appears in the component that displays API keys, and translations are added for many languages. There is no change to how keys are generated, stored, or validated on the server.

AI review queueddocs(guide): fix mangled LNPay webhook example markdown (#4071)by Bartok · b5454f3a · Jul 20, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Bartok

docs(guide): fix mangled LNPay webhook example markdown (#4071)

Co-authored-by: Sera (Bartok9) <sera@local>

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

This commit fixes a broken Markdown link in the documentation. The old example accidentally swapped the link text and URL, making the clickable text show a raw code snippet and the link destination point to literal placeholder text. The patch simply rewrites the example as plain code text so readers can copy the correct webhook URL pattern. There is no code change and no security issue.

AI review queuedfeat: advanced wasm extension features (#4059)by Vlad Stan · f5989201 · Jul 20, 2026 · 33 filesMessage 65 · AdequateLow 38Details
Commit message · Vlad Stan

feat: advanced wasm extension features (#4059)

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

This commit adds new capabilities to LNbits' WebAssembly (WASM) extension system, including public storage appending, public storage pagination, extension-local websockets, and admin permission policy overrides. It also introduces an 'owner context' mode for WASM API routes. The changes are broad and touch many security-sensitive areas (permissions, storage, websockets, route handling), but the diff shows substantial validation and rate-limiting code. Because this is a large feature commit rather than a documented bug fix, it is difficult to tell from the diff alone whether the new security boundaries are fully correct.

Lower-priorityfix: mark expired incoming invoices as failed and add periodic cleanup (#3867)by Morata · a85a5144 · Jul 16, 2026 · 4 filesMessage 85 · StrongTriage 0Details
Commit message · Morata

fix: mark expired incoming invoices as failed and add periodic cleanup (#3867)

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
Lower-priorityfix: payment filter for time range (#4023)by Tiago Vasconcelos · 84bf8558 · Jul 16, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · Tiago Vasconcelos

fix: payment filter for time range (#4023)

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: Infinite invoice listener loop with VoidWallet (#4061)by blackcoffeexbt · 09c6e723 · Jul 15, 2026 · 1 fileMessage 70 · AdequateInformational 24Details
Commit message · blackcoffeexbt

fix: Infinite invoice listener loop with VoidWallet (#4061)

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

This commit removes a method from LNbits' VoidWallet (a fake/test wallet) that was causing an infinite loop when listening for paid invoices. The removed method repeatedly yielded empty invoice IDs, which could make background invoice-listener tasks spin forever. This is a reliability/bug-fix change rather than a direct security vulnerability, but infinite loops in background services can waste resources and potentially affect availability.

AI review queuedfix: UX disable "Send" button after clicking when paying LUD16 (#4034)by blackcoffeexbt · 53a1ae5e · Jul 15, 2026 · 5 filesMessage 70 · AdequateLow 26Details
Commit message · blackcoffeexbt

fix: UX disable "Send" button after clicking when paying LUD16 (#4034)

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

This commit is a small user-experience fix for the LNbits wallet. When a user clicks the 'Send' button to pay a LUD16 (Lightning Address) invoice, the button is now disabled while the payment is being processed. This prevents accidental double-clicks that could send the same payment twice. The change is framed as a UX improvement, not a security fix, but it does reduce the risk of accidental duplicate payments caused by a fast or impatient user clicking the button more than once.

AI review queuedfeat: Extensions for all (#4021)by Vlad Stan · 61ed636d · Jul 15, 2026 · 84 filesMessage 80 · StrongModerate 62Details
Commit message · Vlad Stan

feat: Extensions for all (#4021)

Co-authored-by: alan <alan@lnbits.com>
Co-authored-by: Tiago Vasconcelos <talvasconcelos@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
second-pass: unusually broad change
AI analysis · Moderate 62/100

This is a large feature commit that adds a new 'WASM extensions' system to LNbits, allowing extensions to run as sandboxed WebAssembly modules instead of Python code. It introduces permission checks, runtime limits, and sandboxed APIs for storage, wallet access, HTTP requests, and background payments. Because this is a brand-new, complex subsystem touching security-critical code (payments, wallets, extension installation, admin controls), it carries significant security risk, but the commit itself is a feature addition rather than a disclosed vulnerability fix. There is no evidence in the commit or supplied references that this is a known security issue or that a CVE exists.

Lower-priorityfeat: add emailConfigured to PublicSettings (#4047)by Nathan Day · 43900dd6 · Jul 13, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · Nathan Day

feat: add emailConfigured to PublicSettings (#4047)

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
Lower-priorityMerge commit from forkby Riccardo Balbo · 06c55321 · Jul 13, 2026 · 3 filesMessage 53 · ThinTriage 0Details
Commit message · Riccardo Balbo

Merge commit from fork

* fix: daily withdrawal limit

* feat: unit tests for cumulative daily withdrawal

53/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
merge-commit duplicate discount
Lower-priorityfeat: optimise Uvicorn Settings for heavy web socket use (#4028)by Nathan Day · fc73d83b · Jul 13, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Nathan Day

feat: optimise Uvicorn Settings for heavy web socket use (#4028)

Co-authored-by: dadofsambonzuki <dadofsambonzuki@users.noreply.github.com>
Co-authored-by: dni <office@dnilabs.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
AI review queuedMerge commit from forkby Riccardo Balbo · 4cb743d9 · Jul 13, 2026 · 1 fileMessage 28 · OpaqueModerate 57Details
Commit message · Riccardo Balbo

Merge commit from fork

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
merge-commit duplicate discountsecond-pass: opaque commit message
AI analysis · Moderate 57/100

This commit changes the order of checks when an admin deletes a user account. Previously, the code deleted the user's wallets before checking whether the target was the super-user or another admin. Now it performs those permission checks first. The change prevents an admin from partially deleting wallets belonging to the super-user or another admin before the operation is rejected. It is a hardening fix, but the commit message gives no security context.

Lower-priorityfix: docker image dont rebuild after restart (#4057)by dni ⚡ · 3b6e87b0 · Jul 13, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · dni ⚡

fix: docker image dont rebuild after restart (#4057)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-prioritytest: fix revolut test timestamp exceeded (#4054)by dni ⚡ · 09e44f18 · Jul 13, 2026 · 1 fileMessage 75 · AdequateTriage 0Details
Commit message · dni ⚡

test: fix revolut test timestamp exceeded (#4054)

75/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-prioritychore: make bundle (#4045)by Vlad Stan · cabb58f8 · Jul 8, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Vlad Stan

chore: make bundle (#4045)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body