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 18 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 queuedfix: wallet page `g.user` (#3611)by dni ⚡ · a0e4a594 · Dec 2, 2025 · 2 filesMessage 65 · AdequateLow 27Details
Commit message · dni ⚡

fix: wallet page `g.user` (#3611)

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

This commit is a small frontend bug fix in the LNbits wallet page. The change appears to correct how the current user object (`g.user`) is accessed when selecting which wallet to display. Without the surrounding code context it is hard to tell exactly what was wrong, but the title and the touched files suggest a JavaScript reference error rather than a server-side security flaw.

AI review queuedfeat: add dynamic errorpage (#3602)by dni ⚡ · eefaf3c5 · Dec 2, 2025 · 20 filesMessage 65 · AdequateInformational 18Details
Commit message · dni ⚡

feat: add dynamic errorpage (#3602)

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

This commit adds a new dynamic error page to the LNbits web application. The only server-side change is adding '/error' as a valid route that returns the same HTML response as the public homepage. The rest of the changes are front-end UI components, styles, and bundled JavaScript. There is no obvious security vulnerability introduced, but the change is a partial view of a larger feature, so we cannot fully assess whether the error page safely handles user-supplied data.

AI review queuedfeat: all <img> beeing lazyloaded (#3610)by dni ⚡ · 89cabda1 · Dec 2, 2025 · 5 filesMessage 65 · AdequateInformational 15Details
Commit message · dni ⚡

feat: all <img> beeing lazyloaded (#3610)

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 swaps standard HTML <img> tags for Quasar's <q-img> component across a handful of Vue templates so images are lazy-loaded (loaded only when they come into view). It is a routine performance/user-experience change with no apparent security relevance.

AI review queuedfix: g.wallet artifacts in lnbits-payment-list and lnbits-manage-wall... (#3601)by dni ⚡ · ad8b70a0 · Dec 1, 2025 · 4 filesMessage 70 · AdequateLow 27Details
Commit message · dni ⚡

fix: g.wallet artifacts in lnbits-payment-list and lnbits-manage-wall... (#3601)

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 updates the LNbits web frontend's JavaScript and Vue components. The title says it fixes leftover references to 'g.wallet' in two components (payment list and wallet list). The bundled/minified JavaScript file is also regenerated. There is no clear security issue visible in the diff itself; it appears to be a frontend cleanup or bug-fix change.

AI review queuedfeat: move qrcode scanner into reuseable component (#3567)by dni ⚡ · 64492760 · Nov 28, 2025 · 12 filesMessage 85 · StrongInformational 15Details
Commit message · dni ⚡

feat: move qrcode scanner into reuseable component (#3567)

Co-authored-by: Tiago Vasconcelos <talvasconcelos@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 · Informational 15/100

This commit is a routine frontend refactoring: it extracts the QR-code scanner used on the wallet page into a reusable Vue component. There is no security-relevant change visible in the diff—no new permissions, no altered API calls, no credential handling, and no change to how camera data is processed. It is purely code organisation.

AI review queuedfix: wallet chart render racecondition (#3595)by dni ⚡ · b5f3a46f · Nov 27, 2025 · 2 filesMessage 65 · AdequateInformational 16Details
Commit message · dni ⚡

fix: wallet chart render racecondition (#3595)

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 fixes a frontend display issue where wallet charts could render incorrectly or show stale data because multiple updates were racing against each other. It is a user-interface bug fix, not a security patch, and does not appear to allow an attacker to steal funds or access data.

AI review queuedrefactor: use `utils.copytext` (#3590)by dni ⚡ · 704e5a1b · Nov 27, 2025 · 17 filesMessage 65 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: use `utils.copytext` (#3590)

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 code cleanup that replaces direct copy-to-clipboard calls with a shared utility function called `utils.copytext`. It only touches frontend JavaScript/Vue files and does not change any security-sensitive behavior. There is no indication this fixes or introduces a security issue.

AI review queuedrefactor: move copyText and formatBalance into utils (#3584)by dni ⚡ · e6ca8a33 · Nov 27, 2025 · 9 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: move copyText and formatBalance into utils (#3584)

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 is a routine code cleanup (refactor) that moves two small helper functions, copyText and formatBalance, into a shared utility file. There is no security-relevant change and no indication it fixes or introduces a vulnerability.

AI review queuedfeat: remove selectWallet and use path params instead of url params (#3591)by dni ⚡ · 9c257aa2 · Nov 27, 2025 · 12 filesMessage 70 · AdequateLow 25Details
Commit message · dni ⚡

feat: remove selectWallet and use path params instead of url params (#3591)

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

This commit changes how the LNbits web app selects a wallet: instead of passing the wallet ID as a URL query parameter (e.g., /wallet?wal=abc123), it moves toward using the wallet ID as part of the URL path (e.g., /wallet/abc123). The change is described as a feature/cleanup and does not, on its own, appear to fix a security vulnerability. It may slightly reduce accidental sharing of wallet IDs in browser history/referrer logs, but there is no direct evidence of a security fix.

AI review queuedfix: regression receive dialog was not closing (#3587)by dni ⚡ · a509eb8f · Nov 26, 2025 · 5 filesMessage 80 · StrongInformational 18Details
Commit message · dni ⚡

fix: regression receive dialog was not closing (#3587)

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

This commit fixes a user-interface bug where the 'receive' dialog box in the LNbits wallet would not close after an invoice was created. It is a frontend-only regression fix with no apparent security implications.

AI review queuedchore: move decryptLnurlPayAES to utils (#3576)by dni ⚡ · 49cc8104 · Nov 26, 2025 · 8 filesMessage 65 · AdequateInformational 15Details
Commit message · dni ⚡

chore: move decryptLnurlPayAES to utils (#3576)

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 code cleanup: it moves a helper function called decryptLnurlPayAES from one JavaScript file to a shared utilities file and updates the places that use it. There is no change to what the function does, no new features, and no visible security fix or vulnerability introduced.

AI review queuedfeat: change utils.formatDate and utils.formatTimestamp (#3583)by dni ⚡ · f1f6af0e · Nov 26, 2025 · 17 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

feat: change utils.formatDate and utils.formatTimestamp (#3583)

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 changes how dates and timestamps are formatted in the LNbits web interface. It updates JavaScript utility functions and replaces their usage across various pages and components. There is no indication this change fixes or introduces any security vulnerability.

AI review queuedfix: show all currency if not specified (#3586)by dni ⚡ · 730ab595 · Nov 26, 2025 · 1 fileMessage 65 · AdequateInformational 18Details
Commit message · dni ⚡

fix: show all currency if not specified (#3586)

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 is a small user-interface fix in a wallet settings dropdown. Previously, if no specific currencies were configured as allowed, the currency selector showed an empty list. Now it falls back to showing the full list of available currencies. There is no indication this is a security issue.

AI review queuedchore: cleanup `LNBITS_DENOMINATION` global var (#3580)by dni ⚡ · c6c67c52 · Nov 26, 2025 · 11 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

chore: cleanup `LNBITS_DENOMINATION` global var (#3580)

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 that removes the old global LNBITS_DENOMINATION variable from the frontend JavaScript and Vue templates, replacing it with a more modern global state pattern. It does not change server behavior, user permissions, or how money is handled. There is no security issue visible in the diff.

AI review queuedfix: button hide fix (#3579)by Arc · d0bf4716 · Nov 26, 2025 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · Arc

fix: button hide fix (#3579)

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 is a tiny user-interface tweak in a wallet web page. It changes the condition that decides whether a row of wallet buttons is shown, removing a check tied to a 'mobileSimple' setting so the buttons are hidden only on small screens. There is no security relevance visible in the code change.

AI review queuedfix: change button label on wallet (#3581)by dni ⚡ · 37ad5154 · Nov 26, 2025 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · dni ⚡

fix: change button label on wallet (#3581)

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 swaps the labels and actions of two buttons on the wallet page. The 'Receive' button now correctly opens the receive dialog and checks whether receiving is allowed, while the 'Send' button now correctly opens the send/parse dialog and checks whether sending is allowed. It is a UI bug fix with no security relevance.

AI review queuedfix: cleanup paymentEvents, simplify websockets (#3570)by dni ⚡ · baa9a357 · Nov 26, 2025 · 6 filesMessage 70 · AdequateLow 31Details
Commit message · dni ⚡

fix: cleanup paymentEvents, simplify websockets (#3570)

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

This commit is a frontend-only cleanup of how LNbits handles WebSocket connections for payment events. The title says it 'cleanup paymentEvents, simplify websockets'. The changed files are all JavaScript bundles and source files in the static folder. There is no server-side code change in the diff provided, and no explicit mention of a security vulnerability. The change appears to be a refactoring to make WebSocket handling simpler and more reliable, which could indirectly reduce bugs but does not by itself introduce or fix a clear security issue.

AI review queuedfix: better naming (#3577)by Arc · 7f114ddc · Nov 26, 2025 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · Arc

fix: better naming (#3577)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 only renames two button labels in the wallet web page and adds icons. The underlying button actions, permissions, and dialog triggers are unchanged. There is no security relevance.

AI review queuedchore: refactor windowMixin, init-app.js, lnbits-theme (#3569)by dni ⚡ · 7a796c65 · Nov 25, 2025 · 8 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

chore: refactor windowMixin, init-app.js, lnbits-theme (#3569)

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 is a routine code cleanup (refactor) of the frontend JavaScript and Vue components that handle the app's theme, startup, and shared window behavior. There is no indication it fixes or introduces a security problem.

AI review queued[perf] pending payments check (#3565)by Vlad Stan · 09106873 · Nov 25, 2025 · 8 filesMessage 68 · AdequateLow 27Details
Commit message · Vlad Stan

[perf] pending payments check (#3565)

Co-authored-by: dni ⚡ <office@dnilabs.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ 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 is a performance improvement for LNbits. It changes how pending payments are checked: instead of automatically rechecking every pending payment every time a user views their payment list, the system now only does so when explicitly requested via a new 'recheck_pending' option. It also adds new database filter operators for including/excluding values. There is no clear security fix here; it is primarily a performance and feature enhancement.

AI review queuedfeat: move `wallet.html` to vue component. FINAL DynamicComponent pr (#3559)by dni ⚡ · 33e2fc2e · Nov 25, 2025 · 19 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

feat: move `wallet.html` to vue component. FINAL DynamicComponent pr (#3559)

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: the wallet page is being rewritten from a server-rendered HTML template into a Vue.js component. The old Jinja template is deleted and the Python route that served it is simplified. There is no indication of a security fix or vulnerability being addressed.

AI review queued[fix] user sorting performance (#3561)by Vlad Stan · d55e2a0e · Nov 25, 2025 · 10 filesMessage 53 · ThinInformational 17Details
Commit message · Vlad Stan

[fix] user sorting performance (#3561)

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

This commit is a performance fix for the user list in the LNbits admin panel. It changes which database columns can be searched and sorted, and adds table-name prefixes to SQL filters to avoid ambiguous column errors when the database joins multiple tables. It also sets a default page size and caps the maximum page size at 1,000 rows. There is no direct evidence in the commit that this fixes an active security vulnerability; it appears to be a routine performance and robustness improvement.

AI review queuedrefactor: lnbits-wallet-extra the expandables in the sidebar (#3550)by dni ⚡ · 233398b5 · Nov 24, 2025 · 10 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: lnbits-wallet-extra the expandables in the sidebar (#3550)

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 refactor for the LNbits wallet page. It moves the expandable sidebar sections into a new reusable Vue component called lnbits-wallet-extra and makes small layout adjustments. There is no indication of a security fix or vulnerability being addressed.

AI review queued[perf] Performance bust paginated search (#3543)by Vlad Stan · 44985cb0 · Nov 21, 2025 · 6 filesMessage 53 · ThinInformational 19Details
Commit message · Vlad Stan

[perf] Performance bust paginated search (#3543)

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

This commit is a performance optimization for paginated database searches. It changes how the total row count is calculated when a known table name is provided, avoiding a slower nested subquery. It also adds a small safety check to ensure the provided table name looks like a valid SQL identifier. There is no direct evidence in the commit that this fixes an active security vulnerability.

AI review queuedrefactor: move to `lnbits-wallet-icon` vue component (#3535)by dni ⚡ · b1a7692c · Nov 21, 2025 · 8 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

refactor: move to `lnbits-wallet-icon` vue component (#3535)

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 wallet icon picker UI into a reusable Vue component called `lnbits-wallet-icon`. The same user-facing edit button and icon/color selection dialog still exist; they are just reorganized into a separate file. There is no visible change to security-sensitive behavior such as authentication, payments, API calls, or data handling.