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.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
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
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
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…
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.
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
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…
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…
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.
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.
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.
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
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.
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…
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.
* fix: align paywall dependencies and test types for lint
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
AI review queuedMerge branch 'safe_http'by Arc · 453e7b66 · Nov 9, 2026 · 4 filesMessage 28 · OpaqueHigh 74Details
Commit message · Arc
Merge branch 'safe_http'
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
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 secrets from itself). Second, it hides secret download headers from non-admin users when listing paywalls, preventing invoice-key holders from stealing credentials. The old code used a basic Python URL fetcher and now uses a safer HTTP client with URL validation and streamed downloads.
Lower-priorityfix: min lnbits versionby Arc · fc3bb465 · Nov 9, 2026 · 1 fileMessage 40 · ThinTriage 0Details
Commit message · Arc
fix: min lnbits version
40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedfix: safe_httpby Arc · d8abb841 · Nov 8, 2026 · 3 filesMessage 30 · OpaqueHigh 76Details
Commit message · Arc
fix: safe_http
30/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · High 76/100
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 forgery risk). It replaces that with a safer HTTP client and validates URLs first. Second, it hides secret API keys and authorization tokens from non-admin users when listing paywalls, so regular users cannot steal credentials embedded in paywall configurations.
Lower-priorityMigrate to Pydantic 2 for LNbits 1.7.0 (#17)by Vlad Stan · 0def8193 · Oct 30, 2026 · 7 filesMessage 68 · AdequateInformational 15Details
Commit message · Vlad Stan
Migrate to Pydantic 2 for LNbits 1.7.0 (#17)
* Migrate to Pydantic 2 for LNbits 1.7.0
* chore: prepare paywall for LNbits 1.7.0
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100
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 this change fixes or introduces a security vulnerability.
* feat: allow fiat payments * add loading state * clearer button label
* chore: update to uv
---------
Co-authored-by: dni ⚡ <office@dnilabs.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
✓ 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
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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.
Lower-priorityfeat: update to v1.0.0 (#10)by dni ⚡ · eb0a0394 · Nov 28, 2024 · 14 filesMessage 88 · StrongTriage 0Details
Commit message · dni ⚡
feat: update to v1.0.0 (#10)
* feat: update to v1.0.0 * fix: update paywall * add hint for using filename * fix: add type
✓ 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
Lower-priorityfix copy download link (#6)by Tiago Vasconcelos · 44f72f17 · Oct 14, 2024 · 1 fileMessage 76 · AdequateTriage 0Details
Commit message · Tiago Vasconcelos
fix copy download link (#6)
* fix copy download link
* Update templates/paywall/index.html
---------
Co-authored-by: dni ⚡ <office@dnilabs.com>
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityMerge pull request #8 from lnbits/set_pendingbugby Arc · 28538101 · Oct 12, 2024 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Arc
Merge pull request #8 from lnbits/set_pendingbug
Fix: pointless set_pending shouldnt exist
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
merge-commit duplicate discount
AI review queuedpointless set_pending shouldnt existby Arc · 6b9f2d58 · Oct 12, 2024 · 1 fileMessage 35 · OpaqueInformational 12Details
Commit message · Arc
pointless set_pending shouldnt exist
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 12/100
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 direct evidence in the commit that this fixes a security vulnerability.
AI review queuedfeat: code quality (#7)by dni ⚡ · 4b3f88e6 · Aug 2, 2024 · 20 filesMessage 48 · ThinInformational 15Details
Commit message · dni ⚡
feat: code quality (#7)
* feat: code quality
* fixes
48/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 · Informational 15/100
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 shadowing built-in variable 'id' to 'paywall_id', and adds a basic test. There is no security fix or vulnerability patch in the diff.
Lower-priorityMerge pull request #5 from lnbits/advanceddescriptionby Arc · 7a2df1cb · May 17, 2024 · 6 filesMessage 58 · ThinTriage 0Details
Commit message · Arc
Merge pull request #5 from lnbits/advanceddescription
Added advanced description
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
AI review queuedAdded advanced descriptionby benarc · 482574a8 · May 15, 2024 · 6 filesMessage 35 · OpaqueInformational 15Details
Commit message · benarc
Added advanced description
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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, user input, or access control was changed, so there is no security issue here.
Lower-prioritychore: bump `min_lnbits_version `by Vlad Stan · 10d9f6c1 · May 14, 2024 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Vlad Stan
chore: bump `min_lnbits_version `
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
✓ 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 queueddoc: add file paywallby Vlad Stan · 6dfa5c35 · Feb 7, 2024 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Vlad Stan
doc: add file paywall
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
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.
Security candidateAdd `File Download` paywall support (#3)by Vlad Stan · 32cfefa3 · Feb 7, 2024 · 8 filesMessage 76 · AdequateLow 48Details
Commit message · Vlad Stan
Add `File Download` paywall support (#3)
* feat: introduce file options
* feat: add file download fields
* feat: save file download configs
* feat: show edit dialog
* feat: add support for `Paywall` update
* fix: paywall update
* feat: add mockup download
* feat: check paywall type
* chore: code format 1
* chore: code format 2
* chore: code format 3
* feat: download private files
* fix: permissions
* chore: code format
* feat: check for payment before allowing download
* feat: use shorter link
* chore: code clean-up
* chore: improve log messages
* chore: ruff stuff
* chore: extra logging
* chore: better error handling
* chore: code format
* feat: add `GET` endpoint for creating an invoice
* feat: add `head` operation for download
* feat: add websocket endpoint for invoice check
* feat: watch for paid invoices
* fix: add `paywall_id` in the path for the websocket
* chore: extra logging
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege state
AI analysis · Low 48/100
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 introduces paywall editing, switches some endpoints to require admin keys, and adds a WebSocket for real-time payment confirmation. There are some security-relevant design choices, but no clear vulnerability is directly introduced by the patch itself.
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.
AI review queuedformatting, and fixupsby dni ⚡ · 09e61557 · Apr 9, 2023 · 7 filesMessage 28 · OpaqueInformational 22Details
Commit message · dni ⚡
formatting, and fixups
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 22/100
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 default 'None' value from two invoice-related endpoints so they now require a paywall ID. These changes are minor hardening: they make the API reject missing or wrong-typed inputs more cleanly, but they do not appear to fix an active vulnerability.