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

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

EP8f1d9c34 View source ↗
Public commit record

What the developer wrote

Authored by dependabot[bot]

93/100 · Strong
build(deps-dev): bump webpack in /src/wasm_package

Bumps [webpack](https://github.com/webpack/webpack) from 5.94.0 to 5.105.0.
- [Release notes](https://github.com/webpack/webpack/releases)
- [Changelog](https://github.com/webpack/webpack/blob/main/CHANGELOG.md)
- [Commits](https://github.com/webpack/webpack/compare/v5.94.0...v5.105.0)

---
updated-dependencies:
- dependency-name: webpack
dependency-version: 5.105.0
dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
✓ 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
The short version

What changed, and why it matters

This is a routine automated update by Dependabot that bumps the webpack JavaScript build tool from version 5.94.0 to 5.105.0 inside the WebAssembly package directory. It only changes the package-lock.json lockfile and does not alter any of the project's own cryptographic or wallet code. The update is a development dependency, so it only affects how the package is built, not what end users run in production. There is no indication in the commit that this fixes a specific security vulnerability.

Recommended action

Treat as a normal dependency maintenance update. Review the webpack 5.94.0 to 5.105.0 release notes for any security fixes if desired, and run the usual CI/build tests before merging. No urgent security action is indicated by this commit alone.

Security signals we found

01

dependency version bump only

02

development dependency only (dev: true)

03

no source code or build script changes

04

no vendor security advisory or CVE referenced in commit

05

no mention of vulnerability fix in commit message

Risk score

Why this scored 16/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 8/10
Evidence quality 2/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.

More from libwally-core

Related watches

Informational 15 AI analysisMessage 93 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

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

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 l…

834987a8by dependabot[bot]+65−511 file
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 93 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

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

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…

Dependency update for a known URI-parsing libraryfast-uri 3.1.7 is associated with a fix for a malformed-URI parsing issue (CVE-2025-24035)Only package-lock.json changed; no application code modified
05843a61by dependabot[bot]+8−71 file
No security note in commit
Open full analysis →Source commit ↗
Low 40 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: return an error if fetching input_amount when not present

This commit changes a library function so that it now returns an error when a PSBT/PSET input amount is missing, instead of silently returning zero. It also adds a new 'has_input_amount' check so callers can ask whether the value exists be…

API behavior change: missing field now returns error instead of default zeroAdds presence-check accessor to prevent callers from reading unset valuesABI break noted by vendor
fa3a5859by Jon Griffiths+44−108 files
No security note in commit
Open full analysis →Source commit ↗