EP
← All projectsElements Project

libwally-core

Cross-platform wallet primitives for keys, addresses, transactions, PSBT, and Elements.

BitcoinCryptographic librariesSoftware walletsNormal
Repository coverage

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

35security candidates39second-pass queue128AI analyses
42commits · 30 days
43commits · 60 days
99commits · 180 days
138commits · 365 days
Backfill bands
Aug 5 → Feb 622 seen3 candidatesComplete
Feb 6 → Jun 652 seen3 candidatesComplete
Jun 6 → Jul 67 seen0 candidatesComplete
Jul 6 → Aug 514 seen1 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.

61/100 average clarity
19Strong · 80–100
63Adequate · 60–79
59Thin · 40–59
13Opaque · 0–39
1security candidate 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.
Jon Griffiths12427102158
kkdao444075
odudex514069
Erick Cestari1110100
KY-U111075
Ondřej Češka111050
dependabot[bot]808093
pythcoiner301063
Daniel Newton202055
Greg Sanders101068
Leonardo Comandini101060
longhutianjie101072
Analysis record

Published AI watches

Last scanned 47 minutes ago

Low 40 AI analysisMessage 75 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: allow unknowns (global, input and output) to have empty values.

This commit fixes a bug in how the library reads partially-signed Bitcoin transactions (PSBTs). Previously, if a PSBT contained an unknown extra field with an empty value, the library would store a dangling pointer to a zero-length buffer …

Use of potentially dangling pointer for zero-length bufferMemory-safety bug in PSBT deserializationAddition of regression test for malformed/edge-case PSBT input
10670278by Jon Griffiths+9−23 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

Bump version to 1.6.1

This commit only updates version numbers across build files, documentation, and package metadata from 1.6.0 to 1.6.1. There are no code logic changes, no bug fixes, and no security-related modifications.

f7b0a15bby Jon Griffiths+12−129 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: add add tx_input_is_issuance/tx_is_input_issuance to determine issuance inputs

This commit adds two new helper functions that let callers ask whether a transaction input is an 'issuance' input on the Elements sidechain. It is a straightforward feature addition: it exposes existing internal data through a new API, mir…

91689c1cby Jon Griffiths+42−58 files
No security note in commit
Low 44 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: Copy the PSET genesis blockhash

This commit fixes a bug where cloning or combining a special Bitcoin transaction format (PSET) dropped the 'genesis blockhash' field. Without that field, valid signatures could not be created for certain transactions using Elements taproot…

Missing field copy in PSET clone/combine pathAffects Elements taproot signature hash computationCould produce an unsignable or invalidly-signed PSET
4b64af46by kkdao+3−01 file
No security note in commit
Moderate 60 AI analysisMessage 68 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: Refuse upgrading a v0 PSBT with no tx

This commit fixes a crash bug in libwally-core, a Bitcoin/Elements cryptography library. When a user tried to upgrade an older-style PSBT (Partially Signed Bitcoin Transaction) to version 2, the code would follow a pointer to transaction d…

NULL pointer dereference in transaction-version upgrade pathMissing input validation on internal object state before pointer dereferenceConsistency fix aligning with existing psbt_build_tx() and v0 error handling
e76b2304by kkdao+10−02 files
No security note in commit
Low 49 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

mem: use wally_memcpy for more secret/potentially secret data

This commit replaces ordinary memory-copy operations with a special secure-copy function (wally_memcpy) in a handful of places that handle private keys, BIP32 extended keys, and descriptor template secrets. The goal is to reduce the chance…

secret-data handling (private keys, BIP32 extended keys, SLIP77 blinding key)use of hardened memory-copy primitive (wally_memcpy)defensive hardening against compiler optimization of sensitive copies
473b9161by Jon Griffiths+8−83 files
No security note in commit
Informational 19 AI analysisMessage 65 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: add tx_input_is_pegin/tx_is_input_pegin to determine pegin inputs

This commit is a routine API cleanup: it adds two new functions with clearer names for checking whether a transaction input is a 'pegin' (a special type of cross-chain input used in Elements-based blockchains), and marks the old function n…

1576afb5by Dmytro Hladkykh+48−1610 files
No security note in commit
Low 45 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: Refuse v2 global tx under loose parsing

This change fixes a memory leak in the library's handling of a specific kind of invalid Bitcoin transaction file (PSBT v2 with an unexpected global transaction). Previously, parsing such a file under loose parsing could allocate memory for…

Memory leak on parsing malformed PSBT v2 with global txInvalid PSBT v2 accepted under loose parsing flagPointer overwrite after allocation in psbt_set_global_tx / v2 path
10f41d80by kkdao+17−13 files
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

Add 1.6.0 upgrade advice to CHANGES.md

This commit only updates the project's changelog text (CHANGES.md) to match the published 1.6.0 release notes. It adds a sentence telling users that the release contains important bug and security fixes and that they should update. No code…

7f8f89e8by kkdao+3−01 file
Vendor flagged security relevance
Moderate 60 AI analysisMessage 78 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: fix finalizing large P2SH and bare multisig inputs

This commit fixes two bugs in how the library finalizes old-style multi-signature Bitcoin transactions. First, large multisig setups (like 5-of-5 or 4-of-7) were silently left unfinished because the buffer used was too small. Second, for b…

Buffer size mismatch causing silent failure to finalize large multisig inputsIncorrect scriptSig construction for bare multisig producing invalid spendsHeap allocation introduced to replace undersized stack buffer
cf8eb142by odudex+136−82 files
No security note in commit
Informational 22 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: allow getting the weight and vsize of partial transactions

This commit fixes a bug where two helper functions for calculating transaction size/weight would incorrectly reject transactions that were still being built (for example, when a wallet is estimating fees before all inputs and outputs are a…

Behavior change in argument validation pathRelaxation of a previously added strict checkNo memory safety, cryptographic, or authorization changes visible
01d53ac9by odudex+44−22 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

Bump version to 1.6.0

This commit is a routine version bump from 1.5.6 to 1.6.0. It only changes version numbers in build files, documentation, and package metadata. There are no code changes that affect security.

530eb957by Jon Griffiths+14−149 files
No security note in commit
Low 35 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: prevent pre-bip144 serialization on elements, share arg checks

This commit tightens and unifies how transaction serialization arguments are checked in libwally-core. It prevents a caller from accidentally producing ambiguous pre-BIP144 transaction formats on Elements-based networks, and makes the leng…

Inconsistent argument validation between length and serialization functionsBehavior change for Elements: pre-BIP144 flag is now ignored rather than honoredDefensive unification of transaction serialization checks
063c195dby Jon Griffiths+33−221 file
No security note in commit
Low 47 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: disallow hybrid pubkeys

This commit tightens public-key validation inside PSBT (Partially Signed Bitcoin Transaction) handling by rejecting 'hybrid' public keys. Hybrid keys are an old, non-standard encoding that sits between compressed and uncompressed formats. …

Rejects non-standard hybrid public-key encoding in transaction-related dataNarrows public-key acceptance to only compressed/uncompressed standard encodingsApplies consistent strict validation across keypath, signature, and blinding pubkey paths
06fba283by Jon Griffiths+4−42 files
No security note in commit
Informational 23 AI analysisMessage 83 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

expose ec_public_key_strict_verify to verify non-hybrid pubkeys

This commit adds a new public function that lets callers check whether a Bitcoin-style public key is valid and is not an old, rarely-used 'hybrid' key format. It does not change existing behavior; it only exposes a new, stricter verificati…

New strict public-key validation API rejecting hybrid (0x06/0x07 prefixed uncompressed) public keysHybrid keys are still accepted by the pre-existing wally_ec_public_key_verify; only the new strict call rejects themNo buffer overflow, memory corruption, or cryptographic flaw visible in the diff
e9ff9b8eby Jon Griffiths+39−09 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

bip39: document that mnemonic/passphrase arguments require ascii/utf8 nfkd

This commit only updates documentation comments in a header file. It adds a note that BIP39 mnemonic and passphrase arguments must be ASCII or UTF-8 NFKD encoded. No code behavior changed, no bug was fixed, and no security vulnerability wa…

abbe03ceby Jon Griffiths+6−61 file
No security note in commit
Moderate 51 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

bip39: fail if the callers requested language is not found

This commit fixes a behavior in the BIP39 (mnemonic seed phrase) code where, if a caller asked for a language that wasn't supported, the library would quietly give them the English wordlist instead of reporting an error. The patch makes th…

Silent fallback to default language could cause language/cross-check mismatchesBehavioral change from permissive fallback to explicit failurePotential downstream impact if callers previously passed invalid language strings and relied on English fallback
9f912adaby Jon Griffiths+8−41 file
No security note in commit
Informational 14 AI analysisMessage 93 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

build(deps-dev): bump fast-uri from 3.1.7 to 3.1.9 in /src/wasm_package

This is an automated Dependabot update that bumps a JavaScript development dependency called fast-uri from version 3.1.7 to 3.1.9 inside the WebAssembly packaging directory. The change only updates a package-lock.json file. There is no dir…

Dependency bump of a URI-parsing library, which is a component class commonly associated with input-validation vulnerabilitiesNo explicit security claim, CVE, or advisory reference in the commit or supplied materialsNo source code changes beyond lockfile metadata
9bfb5c78by dependabot[bot]+6−61 file
No security note in commit
Moderate 64 AI analysisMessage 95 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

sign: verify schnorr sigs after creation

This commit adds a safety check when creating Schnorr digital signatures in libwally-core. After a signature is generated, the code now immediately verifies it using the corresponding public key. If the signature fails verification, it is …

Schnorr signature verification immediately after signingOutput buffer cleared when signature generation or verification failsPrivate-key leakage risk explicitly mentioned in commit message
4e3d596fby Jon Griffiths+8−11 file
Vendor flagged security relevance
Low 44 AI analysisMessage 38 · Opaque
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

bip38: fail if aes fails

This commit fixes a programming oversight in the BIP38 encrypted-key code. Previously, the AES encryption/decryption helper functions ignored any error returned by the underlying AES routine. If AES failed for some reason, the code would c…

Unchecked return value from cryptographic primitive (wally_aes) fixedAES failure during BIP38 encryption/decryption could previously produce or accept malformed key materialError propagation added to both encryption and decryption paths
7a723188by Jon Griffiths+26−141 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.

AI review queuedBump version to 1.6.1by Jon Griffiths · f7b0a15b · Nov 11, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.6.1

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

This commit only updates version numbers across build files, documentation, and package metadata from 1.6.0 to 1.6.1. There are no code logic changes, no bug fixes, and no security-related modifications.

AI review queuedtx: add add tx_input_is_issuance/tx_is_input_issuance to determine issuance inputsby Jon Griffiths · 91689c1c · Nov 11, 2026 · 8 filesMessage 50 · ThinInformational 15Details
Commit message · Jon Griffiths

tx: add add tx_input_is_issuance/tx_is_input_issuance to determine issuance inputs

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds two new helper functions that let callers ask whether a transaction input is an 'issuance' input on the Elements sidechain. It is a straightforward feature addition: it exposes existing internal data through a new API, mirroring an already-existing 'pegin' helper. There is no bug fix, no change to parsing rules, and no security-sensitive logic.

AI review queuedmem: use wally_memcpy for more secret/potentially secret databy Jon Griffiths · 473b9161 · Nov 9, 2026 · 3 filesMessage 50 · ThinLow 49Details
Commit message · Jon Griffiths

mem: use wally_memcpy for more secret/potentially secret data

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 49/100

This commit replaces ordinary memory-copy operations with a special secure-copy function (wally_memcpy) in a handful of places that handle private keys, BIP32 extended keys, and descriptor template secrets. The goal is to reduce the chance that sensitive data is left behind in CPU registers or temporary compiler-generated storage. It is a hardening change rather than a fix for a specific, exploitable bug, and the commit message does not claim it resolves a known vulnerability.

AI review queuedtx: add tx_input_is_pegin/tx_is_input_pegin to determine pegin inputsby Dmytro Hladkykh · 1576afb5 · Nov 9, 2026 · 10 filesMessage 65 · AdequateInformational 19Details
Commit message · Dmytro Hladkykh

tx: add tx_input_is_pegin/tx_is_input_pegin to determine pegin inputs

Deprecate tx_elements_input_is_pegin which uses non-standard naming.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit is a routine API cleanup: it adds two new functions with clearer names for checking whether a transaction input is a 'pegin' (a special type of cross-chain input used in Elements-based blockchains), and marks the old function name as deprecated. The old function still works by calling the new one. There is no bug fix or security change visible in the code.

AI review queuedtx: allow getting the weight and vsize of partial transactionsby odudex · 01d53ac9 · Nov 3, 2026 · 2 filesMessage 73 · AdequateInformational 22Details
Commit message · odudex

tx: allow getting the weight and vsize of partial transactions

'tx: prevent pre-bip144 serialization on elements, share arg checks'
applies the serialization checks when computing tx lengths, so
wally_tx_get_weight and wally_tx_get_vsize, which take no flags, fail for
txs without inputs or outputs, e.g. when estimating fees while building a
tx. Apply the serialization checks only when getting the serialized length.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 22/100

This commit fixes a bug where two helper functions for calculating transaction size/weight would incorrectly reject transactions that were still being built (for example, when a wallet is estimating fees before all inputs and outputs are added). The fix narrows where a strict serialization check is applied, so size estimates work on partial transactions again. There is no indication this is a security vulnerability or that it can be exploited.

AI review queuedBump version to 1.6.0by Jon Griffiths · 530eb957 · Nov 1, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.6.0

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

This commit is a routine version bump from 1.5.6 to 1.6.0. It only changes version numbers in build files, documentation, and package metadata. There are no code changes that affect security.

AI review queuedtx: prevent pre-bip144 serialization on elements, share arg checksby Jon Griffiths · 063c195d · Oct 31, 2026 · 1 fileMessage 73 · AdequateLow 35Details
Commit message · Jon Griffiths

tx: prevent pre-bip144 serialization on elements, share arg checks

Ignore the pre-bip144 flag rather than erroring, to make it easier when
coding for both networks.

Share the arg checks so the length functions return consistent values.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 35/100

This commit tightens and unifies how transaction serialization arguments are checked in libwally-core. It prevents a caller from accidentally producing ambiguous pre-BIP144 transaction formats on Elements-based networks, and makes the length-calculation and byte-output functions agree on what inputs are valid. The change is defensive hardening rather than a clear-cut fix for an active vulnerability.

AI review queuedbuild(deps-dev): bump fast-uri from 3.1.7 to 3.1.9 in /src/wasm_packageby dependabot[bot] · 9bfb5c78 · Oct 30, 2026 · 1 fileMessage 93 · StrongInformational 14Details
Commit message · dependabot[bot]

build(deps-dev): bump fast-uri from 3.1.7 to 3.1.9 in /src/wasm_package

Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.7 to 3.1.9.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](https://github.com/fastify/fast-uri/compare/v3.1.7...v3.1.9)

---
updated-dependencies:
- dependency-name: fast-uri
dependency-version: 3.1.9
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 14/100

This is an automated Dependabot update that bumps a JavaScript development dependency called fast-uri from version 3.1.7 to 3.1.9 inside the WebAssembly packaging directory. The change only updates a package-lock.json file. There is no direct evidence in the commit that this fixes a security issue, but version bumps of URI-parsing libraries can sometimes address security bugs in upstream releases.

AI review queuedbip38: fail if aes failsby Jon Griffiths · 7a723188 · Oct 28, 2026 · 1 fileMessage 38 · OpaqueLow 44Details
Commit message · Jon Griffiths

bip38: fail if aes fails

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 44/100

This commit fixes a programming oversight in the BIP38 encrypted-key code. Previously, the AES encryption/decryption helper functions ignored any error returned by the underlying AES routine. If AES failed for some reason, the code would continue and produce or accept potentially invalid encrypted private-key data. The change makes the helpers return the AES status and makes the callers abort the operation if AES fails, preventing use of corrupted or incorrect key material.

AI review queuedmisc: add missing out parameter initialization for error casesby Jon Griffiths · 0c28f9eb · Oct 27, 2026 · 4 filesMessage 50 · ThinModerate 51Details
Commit message · Jon Griffiths

misc: add missing out parameter initialization for error cases

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 51/100

This commit fixes a pattern where library functions could return an error code without first setting their output parameter to a known value. In C, callers often check only the error code, but if they later read the output variable by mistake it could contain leftover or uninitialized data. The patch makes the library consistently zero out output parameters before returning any error, reducing the chance of subtle bugs or information leaks in downstream wallets and tools.

AI review queuedbuild(deps-dev): bump browserslist in /src/wasm_packageby dependabot[bot] · 834987a8 · Sep 3, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps-dev): bump browserslist in /src/wasm_package

Bumps [browserslist](https://github.com/browserslist/browserslist) from 4.28.1 to 4.28.8.
- [Release notes](https://github.com/browserslist/browserslist/releases)
- [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md)
- [Commits](https://github.com/browserslist/browserslist/compare/4.28.1...4.28.8)

---
updated-dependencies:
- dependency-name: browserslist
dependency-version: 4.28.8
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated update by Dependabot that bumps the version of a JavaScript build tool called browserslist, used only in the WebAssembly packaging part of the project. The change only updates version numbers and metadata in a lock file. There is no indication of a security fix or vulnerability.

AI review queuedbuild(deps-dev): bump fast-uri from 3.1.5 to 3.1.7 in /src/wasm_packageby dependabot[bot] · 05843a61 · Sep 2, 2026 · 1 fileMessage 93 · StrongInformational 14Details
Commit message · dependabot[bot]

build(deps-dev): bump fast-uri from 3.1.5 to 3.1.7 in /src/wasm_package

Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.5 to 3.1.7.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](https://github.com/fastify/fast-uri/compare/v3.1.5...v3.1.7)

---
updated-dependencies:
- dependency-name: fast-uri
dependency-version: 3.1.7
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 14/100

This is a routine automated update by Dependabot that bumps the JavaScript helper library fast-uri from version 3.1.5 to 3.1.7 inside the WebAssembly packaging directory. The commit itself only changes a package-lock.json file and does not alter any of libwally-core's cryptographic or wallet code. The newer fast-uri version is known to fix a URI-parsing bug that could, in some applications, cause a program to hang or behave unexpectedly when processing a malformed URI. Because this dependency is used only in the build/test tooling for the WASM package and is not part of the shipped cryptographic library, the practical security risk to libwally-core users is very low.

AI review queuedbuild(deps-dev): bump fast-uri from 3.1.4 to 3.1.5 in /src/wasm_packageby dependabot[bot] · d3f6adf0 · Aug 5, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps-dev): bump fast-uri from 3.1.4 to 3.1.5 in /src/wasm_package

Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.4 to 3.1.5.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](https://github.com/fastify/fast-uri/compare/v3.1.4...v3.1.5)

---
updated-dependencies:
- dependency-name: fast-uri
dependency-version: 3.1.5
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is an automated dependency update by Dependabot that bumps the JavaScript package fast-uri from version 3.1.4 to 3.1.5 inside the WebAssembly packaging directory. The change only updates version numbers and package hashes in package-lock.json. There is no indication in the commit itself that this fixes a security issue, and no security references were provided.

AI review queuedtests: add tests for parsing invalid der sigsby Jon Griffiths · 824e8a33 · Jul 31, 2026 · 1 fileMessage 55 · ThinInformational 12Details
Commit message · Jon Griffiths

tests: add tests for parsing invalid der sigs

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds new test cases to check that the library correctly rejects malformed cryptographic signatures. It does not change any production code, so by itself it cannot introduce or fix a security vulnerability. It may be related to earlier work that hardened signature parsing, but the diff only contains tests.

AI review queuedbuild(deps-dev): bump fast-uri from 3.1.2 to 3.1.4 in /src/wasm_packageby dependabot[bot] · c25fc5fd · Jul 25, 2026 · 1 fileMessage 93 · StrongInformational 13Details
Commit message · dependabot[bot]

build(deps-dev): bump fast-uri from 3.1.2 to 3.1.4 in /src/wasm_package

Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.2 to 3.1.4.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](https://github.com/fastify/fast-uri/compare/v3.1.2...v3.1.4)

---
updated-dependencies:
- dependency-name: fast-uri
dependency-version: 3.1.4
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 13/100

This is an automated update by Dependabot that bumps the JavaScript helper library fast-uri from version 3.1.2 to 3.1.4 inside the WebAssembly packaging directory. It only changes a package-lock.json file and is marked as a development dependency, meaning it is not part of the core cryptographic library shipped to users. There is no direct evidence in the commit that this fixes a security problem in libwally-core itself, but dependency updates can sometimes address bugs or vulnerabilities in the helper library.

AI review queuedBump version to 1.5.6by Jon Griffiths · 0c41f38f · Jul 11, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.5.6

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

This commit is a routine version bump from 1.5.5 to 1.5.6. It only changes version numbers in build files, documentation, and package metadata. There are no code changes that affect security or functionality.

AI review queuedBump version to 1.5.5by Jon Griffiths · 78499f00 · Jul 9, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.5.5

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

This commit is a routine version bump from 1.5.4 to 1.5.5 across build files, documentation, and package metadata. It changes only version strings and the build version constant; no code logic is modified.

AI review queuedBump version to 1.5.4by Jon Griffiths · c5591834 · Jun 16, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.5.4

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

This commit is a routine version bump from 1.5.3 to 1.5.4 across build files, documentation, and package metadata. It changes only version strings and constants; no code logic is modified. There is no security-relevant content in the diff.

AI review queuedcmake: add missing definesby Jon Griffiths · be278177 · May 27, 2026 · 2 filesMessage 35 · OpaqueLow 32Details
Commit message · Jon Griffiths

cmake: add missing defines

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 32/100

This commit fixes the CMake build system so it correctly detects several platform features and headers that the library's C code relies on. Before this fix, the CMake build could silently produce a misconfigured library that uses less secure fallback code paths (for example, missing secure memory-zeroing functions or unaligned-access handling). The commit does not change the core cryptographic code itself; it only changes how the build system discovers what the current platform supports.

AI review queuedbuild: remove distutils dependencyby Jon Griffiths · dbaa9393 · May 25, 2026 · 1 fileMessage 47 · ThinInformational 19Details
Commit message · Jon Griffiths

build: remove distutils dependency

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 19/100

This is a tiny build-maintenance change: it replaces the deprecated Python `distutils.sysconfig` module with the newer `sysconfig` module in the package setup script. There is no security vulnerability visible in the diff, no change to cryptographic code, and no disclosed incident. It is a routine compatibility cleanup.

AI review queuedbuild(deps-dev): bump fast-uri from 3.1.0 to 3.1.2 in /src/wasm_packageby dependabot[bot] · 32a17131 · May 9, 2026 · 1 fileMessage 93 · StrongInformational 13Details
Commit message · dependabot[bot]

build(deps-dev): bump fast-uri from 3.1.0 to 3.1.2 in /src/wasm_package

Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.0 to 3.1.2.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](https://github.com/fastify/fast-uri/compare/v3.1.0...v3.1.2)

---
updated-dependencies:
- dependency-name: fast-uri
dependency-version: 3.1.2
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 13/100

This is an automated Dependabot update that bumps the JavaScript development dependency fast-uri from version 3.1.0 to 3.1.2 inside the WebAssembly (WASM) packaging directory. The change only updates a package-lock.json file. There is no direct evidence in the commit that this fixes a security issue, but version bumps of URI-parsing libraries can sometimes address security bugs. Because it is a devDependency used during build/packaging, any risk is likely limited to the build environment rather than end users of the compiled library.

AI review queuedjs: regenerate wrappersby Jon Griffiths · 019385e5 · Apr 15, 2026 · 1 fileMessage 28 · OpaqueInformational 18Details
Commit message · Jon Griffiths

js: regenerate wrappers

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 only updates the TypeScript type-declaration file for the JavaScript/WebAssembly wrapper. It widens many function parameters from 'Buffer|Uint8Array' to 'Buffer|Uint8Array|null', meaning callers are now allowed to pass null. The change is purely in type definitions; the actual C/WASM implementation is not modified here. It makes the API more permissive on paper, which could hide programming mistakes, but it does not by itself create a runtime vulnerability.

AI review queuedBump version to 1.5.3by Jon Griffiths · 43b97bed · Apr 13, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.5.3

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

This commit is a routine version bump from 1.5.2 to 1.5.3 across build files, documentation, and package metadata. No code logic, cryptographic functions, or security behavior changed.

AI review queuedtx: fix output clearing size on tx_input_init_alloc failureby Jon Griffiths · 2b5fc0ec · Apr 9, 2026 · 1 fileMessage 73 · AdequateLow 44Details
Commit message · Jon Griffiths

tx: fix output clearing size on tx_input_init_alloc failure

Reported-by: Jordan Mecom (@jmecom) via https://github.com/jmecom/odo

73/100 · AdequateMessage clarity
✓ Specific, 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 44/100

This commit fixes a small but real bug in a Bitcoin/Elements transaction library. When creating a new transaction input fails, the code was trying to securely wipe memory using the wrong size: it used the size of a transaction output instead of the size of a transaction input. On most systems this means the clearing is ineffective or incomplete, so secret data (like scripts or witness data) could remain in memory longer than intended. It is a memory-clearing bug, not a direct remote exploit, but it weakens a security safeguard.

AI review queuedtx: add missing check for NULL written paramby Jon Griffiths · 53284275 · Apr 9, 2026 · 1 fileMessage 68 · AdequateLow 36Details
Commit message · Jon Griffiths

tx: add missing check for NULL written param

Reported-by: Jordan Mecom (@jmecom) via https://github.com/jmecom/odo

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

This commit fixes a simple but real bug in a transaction helper function. Before the fix, if a caller accidentally passed a null pointer as the output parameter, the library would crash by writing to address zero. The fix adds a standard null check and returns an error instead. It is a defensive hardening change rather than an active remote exploit, but it removes a reliable local crash path.