NousResearch/hermes-agent

Profile export security and safe file writing

Cluster 92457. Data as of

Nothing open on GitHub. Fix merged in #100101 on 1 Sep 2026. Check it covers your case.

The short answer

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

These items address security concerns around profile archive exports, including writing to temp files before renaming to avoid partial writes, ensuring exports do not land in sensitive build contexts, and responding to an exposed credential related to a committed profile archive.

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.

  • #97835 fix(profiles): make_targz writes to a temp file and renames, not the destination directly

    merged to main

    files: hermes_cli/archive_safe.py, tests/hermes_cli/test_archive_safe.py

  • #100101 fix(security): profile exports never land in source or image contexts (resurrect #92689)

    merged to main

    files: .dockerignore, .github/workflows/ci.yaml, .github/workflows/docker.yml, .github/workflows/profile-artifact-check.yml, .gitignore, hermes_cli/cli_commands_mixin.py, hermes_cli/main.py, hermes_cli/profiles.py, hermes_cli/subcommands/profile.py, hermes_cli/web_routers/profiles.py, scripts/ci/check_profile_archive_boundary.py, tests/hermes_cli/test_profile_export_default_path.py, tests/scripts/test_check_profile_archive_boundary.py, website/docs/user-guide/profile-distributions.md

Closed issues · 1
  • Closed#92457security: rotate exposed webhook credential and republish affected images after committed profile archive
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

Merged PRs
#97835, #100101
Closed issues
1
Attempts
0 PRs closed without merging
Fix link checked
1 Sep 2026

For your agent

The same facts, typed.