npm audit fixes reverting after dependency reinstalls

NousResearch/hermes-agent · cluster 116774 · other

Data as of

Nothing open on GitHub. Fix merged in #117599. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #117599. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #117599. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern security vulnerabilities detected by npm audit being reintroduced after Hermes or other dependency updates reinstall Node modules. The work focuses on making audit fixes persist across such updates rather than being silently reverted.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #117599 fix(doctor): agent-browser npm advisories stop resurfacing after every hermes update (#116774, salvage #116910)

    merged to main

    files: hermes_cli/doctor_tools.py, tests/hermes_cli/test_doctor_audit_remedy.py

  • #138024 fix(deps): `hermes doctor` npm audits clear for root, web, ui-tui and the WhatsApp bridge (salvage #136789)

    merged to main

    files: .npmrc, apps/desktop/package.json, package.json, tests-js/package.json, ui-tui/package.json, web/package.json

3 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1 · other 1

  • #116910 fix(doctor): stop prescribing audit fixes that updates revert (#116774) · merged via another change → 9aab6ba, #117599
  • #125715 fix(security): resolve high-severity npm advisories · other
  • #137494 fix(deps): bump pinned packages past their npm audit fix versions · superseded by another PR → cf3f423, #138024
Closed issues · 1
  • Closed#116774[Bug]: npm audit fix for agent-browser does not persist across hermes update — vulnerabilities reintroduced by fresh Node dependency reinstall
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
other
Merged PRs
#117599, #138024
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
14 Oct 2026

For your agent

The same facts, typed.