Cap OSV response body reads to prevent OOM
NousResearch/hermes-agent · cluster 54794 · agent
Data as of
5 open items. Fix attempted, not merged.
The short answer
2open issues
3open PRs
6items grouped
- Known?
- Yes. 6 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 2 issues and 3 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMultiple issues and fixes address unbounded HTTP response body reads in OSV client and MCP OSV malware preflight checks, with an additional fix for scoped npm package tag handling in OSV checks.
Open issues2
Open PRs3
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#57462 fix(security-audit): cap OSV response body size to prevent OOM (#54794) · superseded by another PR →
#54795,#54794
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging