NousResearch/hermes-agent

npm audit doctor behavior with min-release-age cooldown

Cluster 78893 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

These items concern a bug and related fixes around the doctor command's npm audit remediation becoming ineffective or erroring when a min-release-age constraint is active in .npmrc. The work involves surfacing clearer explanations and annotations about the cooldown's effect on remediation.

Open issues1

  • Issue#78893[Bug]: doctor's npm-audit remediation is unusable under the repo's own .npmrc min-release-age=14 — no-op, then ETARGET on --force

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 2

  • #78939 fix(doctor): explain npm audit release-age cooldown · duplicate → #78938, #78893
  • #79028 fix(doctor): annotate npm audit remediation affected by min-release-age cooldown · duplicate → #78938
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.67: 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
hermes cli
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.