{"repo":"NousResearch/hermes-agent","public_id":"78893","display_label":"npm audit doctor behavior with min-release-age cooldown","summary":"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.","subsystem":"hermes_cli","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":0,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":78893,"title":"[Bug]: doctor's npm-audit remediation is unusable under the repo's own .npmrc min-release-age=14 — no-op, then ETARGET on --force","url":null,"state":"open"},{"kind":"pr","number":78939,"title":"fix(doctor): explain npm audit release-age cooldown","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#78938","number":78938},{"kind":"pr","value":"#78893","number":78893}],"category":"duplicate_of","implication":"duplicate"},"merged":false},{"kind":"pr","number":79028,"title":"fix(doctor): annotate npm audit remediation affected by min-release-age cooldown","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#78938","number":78938}],"category":"duplicate_of","implication":"duplicate"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}