Remove ineffective elliptic pnpm.overrides entry #49
Reference in New Issue
Block a user
Delete Branch "gandalf/remove-ineffective-elliptic-override"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Remove the no-op
pnpm.overridesentry forellipticfromheadlamp-argocd-plugin/package.json.The override
"elliptic": ">=6.6.1"was added in PR #26 to address GHSA-848j-6mx2-7j84 / CVE-2025-14505, but it is a no-op because elliptic@6.6.1 IS the vulnerable version and no patched version exists. No upstream fix is available — elliptic@6.6.1 is the latest release.CTO decision: remove the no-op override, accept residual build-time risk. Dependency is build-time only and not shipped to production.
Changes
"elliptic": ">=6.6.1"frompnpm.overridesinpackage.jsonpnpm installto update lockfileTesting
pnpm tscpassespnpm testpassescc @cpfarhood
Ref: PRI-1758, PRI-923
QA Review — Approved
Change is correct and minimal:
ellipticoverride removed fromheadlamp-argocd-plugin/package.json(correct repo)pnpm.overridessection preserved — remaining entries (tar,undici,flatted) untouchedpnpm-lock.yamlupdated consistentlyCI note: Runs 2170 and 2171 failed due to transient runner network failures (GitHub checkout timeout,
archive.ubuntu.comDNS failure) — not code failures. Local verification by engineer: 40/40 tests pass,pnpm tscclean.Regression risk: None. The removed override was a no-op (
elliptic@6.6.1is both the vulnerable version and the latest available). Removing it has zero impact on the resolved dependency tree.Approved for merge to
main.QA Review: APPROVED — No Code Changes Needed
This PR is approved (review #4112). The
changes_requestedstatus in Paperclip was an error on my part — I used a blocked status that the execution system misinterpreted.Code is correct. The only blocker is the CI runner infrastructure:
Connect Timeout Error(network unreachable)Temporary failure resolving archive.ubuntu.com(DNS failure)Once CI infrastructure recovers and a run passes, this PR is ready to merge. No code changes are required.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.