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 commit only edits the wording of a changelog entry for BTCPay Server 2.4.2. It does not change any code, configuration, or executable files. The edit makes the release sound more urgent, but the commit itself is purely documentation a…
Changelog language changed to describe a critical, actively exploited vulnerability in release 2.4.2No code, configuration, or dependency changes present in the commitSecurity issue is referenced but not fixed or explained in this diff
This commit marks several public methods on ASP.NET Core controllers with [NonAction], which prevents them from being exposed as web-accessible HTTP routes. Without this attribute, these helper methods could be reached directly via URL, po…
Public controller methods exposed as unintended HTTP routesRouting-level access-control hardeningPotential bypass of intended controller action flow
This commit is a version bump and changelog for BTCPay Server 2.4.2. The changelog describes two security-related changes: disabling Basic authentication by default shortly after account creation, and fixing a TOTP two-factor authenticatio…
Vendor describes security fixes in changelogTOTP two-factor authentication bypass via Greenfield Basic authenticationBasic authentication disabled by default after account creation
This commit only adds, removes, and reorders English text strings used for translations and user-interface labels in BTCPay Server. There are no code logic changes, no security settings being enabled or disabled, and no behavior changes. I…
This commit updates several third-party software libraries and a test Docker image to newer versions. It also removes one library (AngleSharp) that was no longer needed. Dependency updates can fix security bugs in those external packages, …
Dependency version bumps for packages that handle HTML sanitization (HtmlSanitizer) and Bitcoin protocol parsing (NBitcoin/NBXplorer)Removal of unused AngleSharp package referenceNo commit-level description of security fixes or CVEs
This change makes BTCPay Server's Greenfield API stop accepting username-and-password 'Basic' authentication by default for existing users. New accounts can still use it for only the first five minutes after creation to set up an API key. …
Disables Basic authentication by default after a 5-minute onboarding windowAdds per-user opt-in flag for Basic auth in data model, API, and UITightens rate-limit bypass to require a recently created account
This commit is a user-interface redesign, not a security fix. It wraps store settings pages in new visual 'section' containers, updates headings and spacing, and adjusts CSS styling. No code behavior, permissions, or data handling changed.
BTCPay Server fixed a bug where accounts protected only by TOTP-based two-factor authentication (2FA) could access the Greenfield API using just an email and password, skipping the second factor. The change now blocks Basic authentication …
This commit adds a user-facing preference feature to BTCPay Server's wallet transactions table: a dropdown that lets users show, hide, and reorder columns. Preferences are saved in the browser's localStorage. The change is a routine UI enh…
No security-relevant keywords in commit title or messagePure client-side UI feature using localStorageNo changes to authentication, authorization, or input processing
This commit changes how BTCPay Server decides whether a Bitcoin transaction input is a SegWit (witness) type when building PSBTs (Partially Signed Bitcoin Transactions). Previously the code only recognized three specific SegWit formats: na…
Broadens SegWit detection from a fixed allow-list to any ScriptType.Witness, mitigating future-version compatibility issuesAdds missing WitnessUtxo population in two wallet PSBT creation pathsWitness UTXO data reduces reliance on NonWitnessUtxo (full previous transaction) for SegWit inputs, which is a known PSBT hardening recommendation
This commit removes a single line that automatically added witness UTXO data to SegWit inputs when decoding a PSBT. The change is titled 'Preserve imported PSBTs,' suggesting the previous behavior was modifying user-supplied transaction da…
PSBT mutation behavior changedWitness UTXO data no longer auto-injected for SegWit inputsPotential data-integrity / non-repudiation consideration for imported PSBTs
This commit fixes a bookkeeping bug in BTCPay Server's multisig (multi-signature) transaction tracker. Previously, a pending transaction could silently collect enough signatures to be finalized, but the system would still label it as 'Pend…
State-machine inconsistency: persisted transaction state could diverge from actual signature countMultisig workflow: incorrect 'Pending' label for a transaction that is actually ready to broadcastNo input validation or authorization changes in the diff
This commit changes BTCPay Server so that when it builds or decodes Partially Signed Bitcoin Transactions (PSBTs), it explicitly adds a compact 'witness UTXO' record for any SegWit inputs. Previously, some SegWit PSBTs may only have carrie…
PSBT data completeness change for SegWit inputsPotential prior state: SegWit PSBTs may have been distributed without witness UTXOsHardware-wallet compatibility / BIP-174 compliance improvement
This commit is a follow-up code review patch for BTCPay Server's pending Bitcoin transaction (multisig) signing feature. It tightens when the service logs a warning versus a debug message after a failed finalization attempt, and it removes…
Logging level change reduces false-warning noise but could mask real finalization failures if SignaturesNeeded is incorrectly zeroRemoval of additionalPsbt parameter prevents accidental combination of an unvalidated extra PSBT into the effective PSBTPer-input signature progress tracking refined to avoid prematurely counting aggregate signatures
This commit is a minor code cleanup that simplifies how BTCPay Server writes log messages when a pending multi-signature transaction fails to finalize. It removes the list of failed input indexes from the log and merges two nearly identica…
This change tightens how BTCPay Server stores signature attempts for multi-signature Bitcoin transactions. Previously, every submitted PSBT (a partially signed transaction file) was kept in history, even if it added no real progress. Now o…
Unbounded history/list growth bounded by logical retention gateResource consumption / storage abuse vector mitigatedLogic change in multi-signature signature collection path
This commit only adds more detailed logging when a pending multi-signature Bitcoin transaction fails to finalize. It does not change how transactions are validated, authorized, or executed. There is no security vulnerability being fixed he…
This commit fixes a bug in BTCPay Server's multisig transaction handling. Previously, the service could get stuck in a 'Pending' state even when enough valid signatures had been collected, because it discarded new signature submissions tha…
Logic flaw in multisig signature collection could leave transactions permanently pending despite sufficient valid signaturesPreviously ignored distinct PSBTs that did not immediately increase signature progressMissing retry of transaction finalization after collecting additional signatures
This commit changes one word in the project's changelog, adding the word 'the' to a bullet point. It is a grammatical typo fix with no effect on software behavior, security, or user data.
This commit changes how BTCPay Server stores invoice comments and metadata. Previously, comments were saved in a separate field and could be updated with a method that was not safe when multiple requests happened at the same time. The patc…
Commit title explicitly describes a race condition fixReplaced read-modify-write metadata update with atomic PostgreSQL jsonb_set operationRemoved dedicated API 'comment' field, narrowing update surface
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-priorityAdding test for unique ReferenceIdby rockstardev · 09b1b895 · Oct 22, 2025 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · rockstardev
Adding test for unique ReferenceId
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityAdding validation of ReferenceId for Payment Requestby rockstardev · aa6944b0 · Oct 22, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · rockstardev
Adding validation of ReferenceId for Payment Request
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedFixup modal not closingby nicolas.dorier · 66a64e86 · Oct 20, 2025 · 1 fileMessage 28 · OpaqueInformational 18Details
Commit message · nicolas.dorier
Fixup modal not closing
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 18/100
This commit fixes a user-interface bug where a confirmation modal dialog would not close properly. The change removes an outer wrapper div that had Bootstrap CSS classes making the modal appear statically and always visible, which prevented the normal modal close behavior. There is no direct evidence in the commit of a security vulnerability such as cross-site scripting or request forgery.
Lower-prioritychore: update status replace logicby Bufo · 49e5afca · Oct 20, 2025 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Bufo
chore: update status replace logic
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
feat: add {Status} template string in redirect url
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidateRefactoring of Webhooks and Email Rules (#6954)by Nicolas Dorier · e8282ca8 · Oct 19, 2025 · 101 filesMessage 53 · ThinLow 27Details
Commit message · Nicolas Dorier
Refactoring of Webhooks and Email Rules (#6954)
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 pathboot or update path
AI analysis · Low 27/100
This is a large refactoring commit that moves BTCPay Server's webhook and email-rule features into separate plugin areas and introduces a new database-backed email-rule system with JSONPath-based conditions. The changes are primarily structural: code is relocated, controllers are renamed, and a new TextTemplate helper is added for email interpolation. There is no explicit security fix or vulnerability disclosure in the commit message or diff, and no direct evidence of an exploitable bug is visible in the supplied materials.
Lower-priorityProviding full status for review in POS recent transactionsby rockstardev · 5ade3b99 · Oct 17, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · rockstardev
Providing full status for review in POS recent transactions
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityCentering the icon for recent transactionsby rockstardev · c630c9b4 · Oct 17, 2025 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · rockstardev
Centering the icon for recent transactions
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd helpers methods (#6941)by Nicolas Dorier · 6b727dd1 · Oct 7, 2025 · 5 filesMessage 43 · ThinTriage 0Details
Commit message · Nicolas Dorier
Add helpers methods (#6941)
43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityAdd ability to setup anti forgery token and action values to confirm modal (#6940)by Nicolas Dorier · e170ed1f · Oct 7, 2025 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Add ability to setup anti forgery token and action values to confirm modal (#6940)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityMinor refactoring (#6939)by Nicolas Dorier · 84c2caf2 · Oct 7, 2025 · 8 filesMessage 43 · ThinTriage 0Details
Commit message · Nicolas Dorier
Minor refactoring (#6939)
43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priority(Refactor) : Converted Selenium test for `CanUseWebhooks` and Others to playwright (#6923)by Abhijay Jain · 5e9dca19 · Sep 22, 2025 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · Abhijay Jain
(Refactor) : Converted Selenium test for `CanUseWebhooks` and Others to playwright (#6923)
* (Test):Converted/Added Playwright Test for CanUseAwaitProgressForInProgressPayout
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Security candidateBetter error message on invalid PSBT in Sign with Seed (#6920)by Nicolas Dorier · fa29176a · Sep 18, 2025 · 2 filesMessage 81 · StrongInformational 23Details
Commit message · Nicolas Dorier
Better error message on invalid PSBT in Sign with Seed (#6920)
* Better error message on invalid PSBT in Sign with Seed
* Improve error reporting if a PSBT built by SendWallet is not signable
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 23/100
This commit improves error messages shown to users when a Bitcoin transaction file (PSBT) cannot be signed because it is malformed or missing required data. It does not change the underlying signing rules; it only reports failures more clearly and redirects the user to an analysis view instead of attempting to sign an invalid PSBT. There is no direct evidence this fixes an exploitable vulnerability.
Lower-priorityRestore old minrelaytxfee for making test passby nicolas.dorier · 790616d2 · Sep 9, 2025 · 2 filesMessage 55 · ThinTriage 0Details
Commit message · nicolas.dorier
Restore old minrelaytxfee for making test pass
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
This commit changes a single translation string in BTCPay Server to include an error placeholder. It is a routine localization update with no security relevance visible in the diff.
✓ 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 15/100
This commit fixes a single-letter capitalization typo in the API documentation file. The property name 'feerate' was changed to 'feeRate' in a Swagger/OpenAPI JSON template so the documented field matches the actual API. There is no code behavior change and no security impact.
Lower-priorityChangelog and Bump to 2.2.1by nicolas.dorier · 350152ca · Sep 9, 2025 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · nicolas.dorier
Changelog and Bump to 2.2.1
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedFix: Date column header isn't aligned (#6914)by Nicolas Dorier · 967626a0 · Sep 9, 2025 · 6 filesMessage 65 · AdequateInformational 15Details
Commit message · Nicolas Dorier
Fix: Date column header isn't aligned (#6914)
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 purely cosmetic UI fix. It adjusts spacing around 'Date' column headers in several admin pages so the header text and a small date-format toggle button line up neatly. There is no security relevance.
Lower-priorityFix: Updating store settings would silently fail where the is validation issueby nicolas.dorier · 0d466251 · Sep 8, 2025 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · nicolas.dorier
Fix: Updating store settings would silently fail where the is validation issue
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
* chore: bump `dotnet/aspnet` base image to 8.0.18
100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
refactor: show error detail in ListPlugins temp data.
42/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body! Contains work-in-progress language