Skip to content

fix(deps): express 4.22.3 in the contract exporter - #61

Merged
moscowchill merged 1 commit into
devfrom
codex/qp-exporter-express
Oct 25, 2026
Merged

moscowchill merged 1 commit into
devfrom
codex/qp-exporter-express

Conversation

@moscowchill

Copy link
Copy Markdown
Contributor

monitoring/contract-exporter moves to express 4.22.3 with body-parser 1.20.9 (GHSA-27r3-jxmh-p828: a compressed request body with trailing bytes stops the process) and proxy-addr 2.0.8 (GHSA-jqcg-44mw-7w3h, critical: trust check bypass with IPv4-mapped IPv6). The exporter is not running anywhere today; this keeps it safe to start. Lockfile-only apart from the express range.

Local: npm ci 0, npm audit --omit=dev leaves only the known zod 3 copy inside @theqrl/web3 (handled separately), node --check src/index.js 0.

body-parser 1.20.9 (GHSA-27r3-jxmh-p828, a compressed body with trailing
bytes stops the process) and proxy-addr 2.0.8 (GHSA-jqcg-44mw-7w3h, trust
check bypass with IPv4-mapped IPv6). The exporter is not deployed today;
this keeps it safe to run.
@moscowchill
moscowchill merged commit 257252f into dev Oct 25, 2026
2 checks passed
@moscowchill
moscowchill deleted the codex/qp-exporter-express branch October 25, 2026 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant