AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

chore: remove extension builder from core (#4331)

Public commit record

What the developer wrote

Authored by Vlad Stan

65/100 · Adequate
chore: remove extension builder from core (#4331)
✓ 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
The short version

What changed, and why it matters

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 and no vulnerability being patched—this is a feature removal (refactoring).

Recommended action

No security action required. If you operate an LNbits instance, note that the Extension Builder feature is no longer available after this commit; users must install extensions through the remaining extension marketplace flow.

Security signals we found

01

Removal of a code-generation feature that used Jinja2 with autoescape=False (bandit S701 was previously suppressed for this file)

02

Removal of an endpoint that allowed admins to build, deploy, and activate extensions from user-supplied JSON configuration

03

Reduction of extension installation attack surface by removing the builder manifest source and preview file-serving route

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.