Track high-severity npm audit findings from Transformers (adm-zip and sharp)

[leonfox28]

Short description

@cortexkit/pi-magic-context@0.33.0 currently produces five HIGH npm audit findings through the @huggingface/transformers dependency tree.

What happened?

Installing Magic Context in Pi's shared extension prefix produces these dependency chains:

@cortexkit/pi-magic-context@0.33.0
└─ @huggingface/transformers@4.2.0
   ├─ onnxruntime-node@1.24.3
   │  └─ adm-zip@0.5.18
   └─ sharp@0.34.5

There are two underlying public advisories:

1. adm-zip GHSA-xcpc-8h2w-3j85: a crafted ZIP can trigger a roughly 4 GB allocation and process-level denial of service. Fixed in adm-zip@0.6.0.
2. sharp GHSA-f88m-g3jw-g9cj: inherited libvips vulnerabilities (CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591). Fixed in sharp@0.35.x.

npm counts the vulnerable packages plus their affected parent chain, resulting in five HIGH findings for Magic Context.

Why consumers cannot resolve it normally

• @huggingface/transformers@4.2.0 pins onnxruntime-node to 1.24.3.
• Current onnxruntime-node releases declare adm-zip: ^0.5.16, which cannot resolve 0.6.0 because of 0.x semver boundaries.
• Transformers declares sharp: ^0.34.5, which similarly cannot resolve patched 0.35.x.
• Consequently, a normal install/update cannot clear these findings without violating upstream ranges.

Upstream status

The problems are already being tracked upstream, so this issue is intended as a downstream release tracker rather than a duplicate vulnerability report:

• adm-zip chain: huggingface/transformers.js#1727
• sharp range: huggingface/transformers.js#1729
• Transformers dependency update PR: huggingface/transformers.js#1731
• ONNX Runtime adm-zip update PR: microsoft/onnxruntime#29772

Expected behavior / suggested follow-up

Once fixed ONNX Runtime and Transformers releases are available, please bump Magic Context's minimum @huggingface/transformers version and publish a patch release so existing Pi extension lockfiles are forced onto the patched dependency tree.

It may also be useful to add a production-dependency audit check so these transitive findings are caught before publication.

Diagnostics

$ npm audit --prefix ~/.pi/agent/npm

adm-zip <0.6.0
Severity: high
No fix available within the currently declared dependency ranges

sharp <0.35.0
Severity: high
No fix available within the currently declared dependency ranges

5 high-severity findings through the Magic Context dependency chain

Plugin version

0.33.0

Platform

macOS arm64, Node.js 24.18.0, npm 11.16.0

Client

Pi