hermes-agent 0.19.0 → 0.20.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/DISCLAIMER.md +15 -16
- package/NOTICE +13 -11
- package/PRIVACY.md +59 -22
- package/README.md +472 -89
- package/SECURITY.md +291 -138
- package/bin/hermes-npm.js +5 -0
- package/lib/npm-channel.js +533 -0
- package/lib/package-metadata.js +1 -1
- package/lib/python-launcher.js +45 -52
- package/lib/upstream-migration.js +336 -0
- package/lib/uv-installer.js +258 -0
- package/package.json +20 -6
- package/scripts/postinstall.js +294 -46
package/DISCLAIMER.md
CHANGED
|
@@ -1,22 +1,21 @@
|
|
|
1
|
-
# Disclaimer
|
|
1
|
+
# Unofficial Package Disclaimer
|
|
2
2
|
|
|
3
|
-
This
|
|
4
|
-
|
|
5
|
-
Hermes Agent is developed by Nous Research:
|
|
3
|
+
This repository and its npm packages are an unofficial bridge for the upstream
|
|
4
|
+
Hermes Agent project:
|
|
6
5
|
|
|
7
6
|
https://github.com/NousResearch/hermes-agent
|
|
8
7
|
|
|
9
|
-
This project is not affiliated with, endorsed by, sponsored by, or maintained
|
|
10
|
-
Nous Research. References to Hermes Agent and Nous Research
|
|
11
|
-
|
|
12
|
-
launches.
|
|
13
|
-
|
|
14
|
-
The npm package name is `hermes-agent` because it installs the upstream Python
|
|
15
|
-
package with the same name. This repository does not claim ownership of the
|
|
16
|
-
upstream Hermes Agent project, its source code, or its trademarks.
|
|
8
|
+
This project is not affiliated with, endorsed by, sponsored by, or maintained
|
|
9
|
+
by Nous Research. References to Hermes Agent and Nous Research identify the
|
|
10
|
+
upstream open-source project that this npm package checks out and launches.
|
|
17
11
|
|
|
18
|
-
|
|
19
|
-
|
|
12
|
+
Each npm release pins an official upstream GitHub Release tag and commit. Users
|
|
13
|
+
may then run the native `hermes update` command, which intentionally moves the
|
|
14
|
+
local checkout independently of npm and may advance it beyond an official
|
|
15
|
+
Release. `hermes-npm update` returns the installation to the npm release
|
|
16
|
+
channel.
|
|
20
17
|
|
|
21
|
-
|
|
22
|
-
|
|
18
|
+
The npm package name is `hermes-agent` because it bridges the upstream project
|
|
19
|
+
with the same name. This repository does not claim ownership of upstream source
|
|
20
|
+
code, project identity, or trademarks. All marks belong to their respective
|
|
21
|
+
owners.
|
package/NOTICE
CHANGED
|
@@ -2,24 +2,26 @@ hermes-agent npm bridge
|
|
|
2
2
|
Copyright (c) 2026 wyrtensi
|
|
3
3
|
License: MIT
|
|
4
4
|
|
|
5
|
-
This repository publishes an unofficial npm bridge for Hermes Agent.
|
|
6
|
-
|
|
7
|
-
|
|
5
|
+
This repository publishes an unofficial npm bridge for Hermes Agent. npm
|
|
6
|
+
release synchronization follows the latest official non-draft,
|
|
7
|
+
non-prerelease GitHub Release from the upstream project.
|
|
8
8
|
|
|
9
9
|
Hermes Agent is developed by Nous Research.
|
|
10
10
|
Upstream repository: https://github.com/NousResearch/hermes-agent
|
|
11
|
-
Upstream
|
|
11
|
+
Upstream releases: https://github.com/NousResearch/hermes-agent/releases
|
|
12
12
|
Upstream license: MIT
|
|
13
13
|
Upstream copyright notice: Copyright (c) 2025 Nous Research
|
|
14
14
|
|
|
15
|
-
This
|
|
16
|
-
|
|
17
|
-
|
|
15
|
+
This repository does not claim ownership of upstream source code, the Hermes
|
|
16
|
+
Agent name, or Nous Research marks. It provides Node.js command shims,
|
|
17
|
+
installation orchestration, release metadata, and an npm-specific update/status
|
|
18
|
+
interface.
|
|
18
19
|
|
|
19
|
-
The npm
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
20
|
+
The published npm tarball contains bridge code, not the upstream source tree.
|
|
21
|
+
During installation, Git fetches the exact upstream Release tag and verifies
|
|
22
|
+
that it resolves to the full commit SHA recorded in package.json. The installed
|
|
23
|
+
checkout remains mutable because `hermes update` intentionally invokes the
|
|
24
|
+
native upstream rolling updater.
|
|
23
25
|
|
|
24
26
|
For the upstream license text, see:
|
|
25
27
|
https://github.com/NousResearch/hermes-agent/blob/main/LICENSE
|
package/PRIVACY.md
CHANGED
|
@@ -1,34 +1,71 @@
|
|
|
1
1
|
# Privacy
|
|
2
2
|
|
|
3
|
-
This npm bridge does not collect telemetry
|
|
3
|
+
This npm bridge does not collect telemetry and does not operate an analytics
|
|
4
|
+
endpoint.
|
|
4
5
|
|
|
5
|
-
|
|
6
|
+
It does not intentionally collect, store, or upload personal information,
|
|
7
|
+
credentials, npm tokens, API keys, repository contents, or shell history.
|
|
6
8
|
|
|
7
|
-
|
|
8
|
-
- analytics events
|
|
9
|
-
- npm tokens
|
|
10
|
-
- GitHub tokens
|
|
11
|
-
- SSH keys
|
|
12
|
-
- API keys
|
|
13
|
-
- repository contents
|
|
14
|
-
- shell history
|
|
9
|
+
## Installation network activity
|
|
15
10
|
|
|
16
|
-
During
|
|
17
|
-
uses the local Node.js runtime, the local Python interpreter, and pip. Its
|
|
18
|
-
network activity is limited to pip downloading the pinned Python package and its
|
|
19
|
-
dependencies from the user's configured Python package index.
|
|
11
|
+
During `npm install`, the bridge may contact:
|
|
20
12
|
|
|
21
|
-
|
|
22
|
-
|
|
13
|
+
- GitHub to fetch the exact upstream Git tag and commit recorded in
|
|
14
|
+
`package.json`;
|
|
15
|
+
- GitHub to download the pinned Astral `uv` release asset;
|
|
16
|
+
- Astral-managed Python distribution endpoints used by `uv`;
|
|
17
|
+
- Python indexes and artifact hosts referenced by upstream project
|
|
18
|
+
configuration and `uv.lock`.
|
|
23
19
|
|
|
24
|
-
|
|
20
|
+
These services receive normal request metadata such as IP address, requested
|
|
21
|
+
resource, TLS metadata, and user agent. The bridge adds no analytics identifier.
|
|
25
22
|
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
23
|
+
The temporary dependency cache is stored inside the npm package runtime and is
|
|
24
|
+
deleted after the installation attempt. The Git checkout, managed Python, and
|
|
25
|
+
venv remain until npm replaces or removes the package.
|
|
26
|
+
|
|
27
|
+
## Update network activity
|
|
28
|
+
|
|
29
|
+
`hermes-npm check` contacts `https://registry.npmjs.org` to read the `latest`
|
|
30
|
+
dist-tag. When an update is approved, `hermes-npm update` installs that exact
|
|
31
|
+
checked version from the same registry. npm can still use applicable proxy, CA,
|
|
32
|
+
authentication, and credential configuration.
|
|
33
|
+
|
|
34
|
+
`hermes update` is the unmodified upstream rolling updater. Its GitHub,
|
|
35
|
+
dependency, backup, gateway, and managed-tool behavior belongs to upstream
|
|
36
|
+
Hermes Agent rather than this bridge. Current upstream code may create a
|
|
37
|
+
managed `uv` under `HERMES_HOME/bin` (normally `~/.hermes/bin`) while updating.
|
|
38
|
+
|
|
39
|
+
## Upstream handoff network activity
|
|
29
40
|
|
|
30
|
-
|
|
41
|
+
`hermes-npm migrate upstream` only prints a plan. With `--yes`, the bridge runs
|
|
42
|
+
the official installer stored in its verified Release checkout. That installer
|
|
43
|
+
may contact GitHub, Astral/Python distribution services, Python package
|
|
44
|
+
indexes, npm/Node distribution services, and browser/tool artifact hosts used
|
|
45
|
+
by upstream. Interactive setup, gateway startup, and Desktop building are
|
|
46
|
+
disabled, but upstream may still install managed prerequisites and seed files
|
|
47
|
+
under `HERMES_HOME`.
|
|
48
|
+
|
|
49
|
+
The handoff preserves existing user state and does not copy it to a bridge
|
|
50
|
+
service. After successful verification it runs npm uninstall for the detected
|
|
51
|
+
scope. Subsequent runtime network behavior belongs to the upstream-managed
|
|
52
|
+
installation.
|
|
53
|
+
|
|
54
|
+
## Runtime boundary
|
|
55
|
+
|
|
56
|
+
The `hermes` and `hermes-agent` commands execute upstream Hermes Agent. Model
|
|
57
|
+
providers, tools, integrations, credentials, telemetry choices, and network
|
|
58
|
+
calls configured there are governed by upstream software and third-party
|
|
59
|
+
services selected by the user.
|
|
60
|
+
|
|
61
|
+
Upstream source: https://github.com/NousResearch/hermes-agent
|
|
62
|
+
|
|
63
|
+
## Auditing without lifecycle execution
|
|
31
64
|
|
|
32
65
|
```bash
|
|
33
|
-
|
|
66
|
+
npm pack hermes-agent
|
|
67
|
+
npm install --ignore-scripts ./hermes-agent-*.tgz
|
|
34
68
|
```
|
|
69
|
+
|
|
70
|
+
After review, provision the runtime with `npm rebuild hermes-agent`, or use
|
|
71
|
+
`npm rebuild --global hermes-agent` for a global installation.
|