horo-next
An unofficial PyPI distribution of Hermes Agent by Nous Research.
Upstream no longer publishes Hermes Agent to PyPI. horo-next rebuilds each upstream release as a pip-installable wheel. It is not affiliated with, endorsed by, or sponsored by Nous Research.
pip install horo-next
hermes
The command is hermes and the data directory is ~/.hermes, as upstream. Do not install horo-next and hermes-agent into the same environment: both provide the same top-level modules.
What differs from upstream
Packaging only. Product behaviour is upstream's.
- Bundled skills and locales are packaged inside the wheel.
- The web dashboard and the terminal UI are prebuilt into the wheel, so they never run
npmon your machine.hermes dashboardneedspip install "horo-next[web]";hermes --tuineeds anodebinary onPATH. hermes updatepoints topip install -U horo-next.- Direct dependencies with a published vulnerability fix are raised to the fixed version. Each release notes which.
- Python 3.11 is kept supported; the upper bound follows each upstream release.
- Dependencies only available from a URL (not on PyPI) are left out and must be installed separately.
- Only the extras that work on an air-gapped network are provided:
web,mcp,acp,cron,pty,uvloop, and a newmattermost. Extras for cloud services and public messaging platforms are not.
Security review
Each release is checked to carry no known vulnerability (OSV) in any dependency. The wheel contains a CycloneDX SBOM (.dist-info/sboms/) naming every Python dependency and every npm package compiled into the dashboard and TUI, and the license texts of the latter. The GitHub release attaches the same SBOM, the audit report and a hashed requirements file. See SECURITY.md.
Versions
horo-next X.Y.Z is built from upstream Hermes Agent vX.Y.Z. A packaging-only fix on the same upstream release is published as X.Y.Z.postN.
Offline installation
Each release attaches requirements-X.Y.Z.txt, the full resolved dependency set. On a machine with internet access:
pip download horo-next==X.Y.Z -d wheelhouse
Then on the offline machine:
pip install --no-index --find-links wheelhouse horo-next
License
MIT. Hermes Agent is copyright Nous Research; bundled skills carry their own licenses.
Metadata
Release files for horo-next 0.21.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| horo_next-0.21.5-py3-none-any.whl | Python 3 | none | any | Details for horo_next-0.21.5-py3-none-any.whl |
Release files / horo_next-0.21.5-py3-none-any.whl
| Download URL | horo_next-0.21.5-py3-none-any.whl |
|---|---|
| Size | 20.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9ebf9fcc9952886c7db3887464e760b2be54c35bfdcbd5b811f3715eb1c0965
|
|
BLAKE2b-256 checksum How to use checksums |
6043eb2ae7ed5c3af5427cbb8ac05bb62cdc30b4ad73b74e6dbad44665e9a352
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for horo-next 0.21.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for horo_next-0.21.5-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.