LN
← All projectsLNbits

LNbits Paywall

Official LNbits extension for paid access to links, content, and downloadable files.

BitcoinLightning NetworkPayment infrastructureElevated watch
Repository coverage

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

1security candidates12second-pass queue14AI analyses
5commits · 30 days
5commits · 60 days
5commits · 180 days
5commits · 365 days
Backfill bands
Nov 8 → May 120 seen0 candidatesComplete
May 12 → Sep 90 seen0 candidatesComplete
Sep 9 → Oct 90 seen0 candidatesComplete
Oct 9 → Nov 81 seen0 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.

51/100 average clarity
5Strong · 80–100
5Adequate · 60–79
8Thin · 40–59
11Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Arc704241
Vlad Stan513063
Tiago Vasconcelos802059
dni ⚡703055
benarc101035
Pavol Rusnak10100
Analysis record

Published AI watches

Last scanned 35 minutes ago

High 74 AI analysisMessage 28 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

Merge branch 'safe_http'

This merge commit hardens LNbits Paywall's file-download feature against two security risks. First, it stops the server from fetching files from internal/private network addresses (so an attacker can't trick the paywall into reading secret…

Server-Side Request Forgery (SSRF) mitigation added via validate_url() and SafeHttpClientSensitive header redaction for non-admin API consumersSwitch from urllib.request.urlopen to safer, streamed HTTP client
453e7b66by Arc+194−64 files
No security note in commit
High 76 AI analysisMessage 30 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

fix: safe_http

This commit fixes two security issues in the LNbits Paywall extension. First, it stops the download feature from using a basic Python URL fetcher that could be tricked into reading files from the server itself (a server-side request forger…

SSRF mitigation: urllib.request.urlopen replaced with SafeHttpClient and validate_url()Credential redaction: file_config.headers hidden from non-admin paywall listingsNew security regression tests for download SSRF, unpaid-download gating, and header visibility
d8abb841by Arc+193−53 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 68 · Adequate
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

Migrate to Pydantic 2 for LNbits 1.7.0 (#17)

This commit is a routine extension migration to support Pydantic 2 and LNbits 1.7.0. It adds the entire paywall extension codebase, configuration, tests, and build tooling. There is no indication in the commit or supplied references that t…

0def8193by Vlad Stan+922−3807 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

Update pyproject.toml

This commit adds a single configuration line to the project's Python packaging file, telling Poetry not to treat the project as an installable package. It is a build/tooling change with no visible security relevance.

06557694by Tiago Vasconcelos+1−01 file
No security note in commit
Informational 12 AI analysisMessage 35 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

pointless set_pending shouldnt exist

This commit removes a single line that marked a payment as 'not pending' when checking whether a paywall payment was made. The change appears to be a code cleanup because the status update was unnecessary during a read-only check. There is…

No security-relevant keywords in commit title or messageChange is a two-line deletion with no added logicNo references, CVEs, or attribution supplied
6b9f2d58by Arc+0−21 file
No security note in commit
Informational 15 AI analysisMessage 48 · Thin
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

feat: code quality (#7)

This commit is a routine code-quality and tooling update for the LNbits Paywall extension. It adds linting/formatting configuration (Black, Ruff, Prettier, mypy, pyright), restructures how FastAPI routers are registered, renames a shadowin…

4b3f88e6by dni ⚡+2850−7620 files
No security note in commit
Informational 15 AI analysisMessage 35 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

Added advanced description

This commit is purely a documentation and metadata update for the LNbits Paywall extension. It adds a longer description, terms-and-conditions text, screenshots, contributor links, and license information. No code that handles payments, us…

482574a8by benarc+48−26 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

doc: add file paywall

This commit only adds documentation to the README explaining that files can also be protected behind a paywall. No code was changed, and there is no security issue visible in the diff.

6dfa5c35by Vlad Stan+5−01 file
No security note in commit
Low 48 AI analysisMessage 76 · Adequate
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

Add `File Download` paywall support (#3)

This commit adds a new 'File Download' paywall feature to the LNbits Paywall extension. It lets sellers charge for access to files hosted elsewhere, with the server fetching the file on behalf of paying customers. The change also introduce…

Server-Side Request Forgery (SSRF) risk: `_file_streamer` fetches user-controlled `file_config.url` with user-controlled `file_config.headers` from the server, potentially allowing internal network probing or credential exfiltration if headers/URL are attacker-controlled.Payment-hash reuse across paywalls is mitigated: `_is_payment_made` now checks `payment.extra.get('id')` matches the requested paywall ID.Authorization elevation: create/update/delete now require admin key instead of any wallet key.
32cfefa3by Vlad Stan+561−1088 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

Update README.md

This commit only updates the README.md file with a more descriptive title and a link to a tutorial. It does not change any code, configuration, or security behavior.

6fa66920by Tiago Vasconcelos+2−11 file
No security note in commit
Informational 22 AI analysisMessage 28 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

formatting, and fixups

This commit is mostly cosmetic reformatting and updating import statements to match newer FastAPI versions. The only functional code changes are adding explicit 'string' type annotations to several web endpoint parameters and removing a de…

route parameters now explicitly typed as strpaywall_id made required instead of optional (Query(None) removed) on invoice creation and invoice check endpointsimport migration from starlette to fastapi modules
09e61557by dni ⚡+21−227 files
No security note in commit
Informational 15 AI analysisMessage 0 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

add license

This commit simply adds a standard MIT open-source license file to the repository. It makes no changes to program code, configuration, or security settings. There is no security issue here.

bed61b36by Pavol Rusnak+21−01 file
No security note in commit
Informational 15 AI analysisMessage 35 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

add github release workflow

This commit adds a standard GitHub Actions workflow that automatically creates a release when a version tag like '1.0' is pushed. It is purely a CI/CD automation change and does not modify application code, user-facing behavior, or securit…

fcb40e23by dni ⚡+19−01 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
LN LNbitsLNbits Paywall BitcoinLightning NetworkPayment infrastructure

Update manifest.json

This commit changes one word in a manifest file, renaming the referenced repository from 'paywall-extension' to 'paywall'. It is a metadata-only update with no code changes and no security relevance.

13b30dc0by Arc+1−11 file
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.

Lower-priorityfix docs #1497 and add gitignoreby dni ⚡ · a7530a04 · Feb 27, 2023 · 2 filesMessage 53 · ThinTriage 0Details
Commit message · dni ⚡

fix docs #1497 and add gitignore

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedadd licenseby Pavol Rusnak · bed61b36 · Feb 24, 2023 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Pavol Rusnak

add license

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit simply adds a standard MIT open-source license file to the repository. It makes no changes to program code, configuration, or security settings. There is no security issue here.

AI review queuedadd github release workflowby dni ⚡ · fcb40e23 · Feb 17, 2023 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · dni ⚡

add github release workflow

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit adds a standard GitHub Actions workflow that automatically creates a release when a version tag like '1.0' is pushed. It is purely a CI/CD automation change and does not modify application code, user-facing behavior, or security controls.

AI review queuedUpdate manifest.jsonby Arc · 13b30dc0 · Feb 10, 2023 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Arc

Update manifest.json

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit changes one word in a manifest file, renaming the referenced repository from 'paywall-extension' to 'paywall'. It is a metadata-only update with no code changes and no security relevance.