horo-next-webui
An unofficial PyPI distribution of Hermes WebUI, the browser interface for Hermes Agent. It is not affiliated with, endorsed by, or sponsored by the Hermes WebUI authors or Nous Research.
pip install horo-next horo-next-webui
hermes-webui
Install it into the same environment as horo-next (Hermes Agent). The command is hermes-webui and state lives in ~/.hermes/webui, as upstream.
What differs from upstream
Packaging and launch only. Product behaviour is upstream's.
- Works offline. Prism, xterm, Mermaid and PDF.js are served from the wheel instead of cdn.jsdelivr.net.
- No known advisories in shipped code at release time, in OSV or Sonatype's public data. Every front-end library is moved to the lowest clean release, and Mermaid is rebuilt from a lockfile so the DOMPurify it embeds is a fixed release too. Python dependency floors that admit a vulnerable version are raised. Each release notes exactly what changed.
- The launcher never installs anything. Without Hermes Agent it tells you to
pip install horo-next, instead of running upstream's GitHub installer or creating a virtualenv inside site-packages. - The server's working directory is the WebUI state directory, not site-packages.
- No automatic outbound traffic. The GitHub update check is off by default, and the CSP names no CDN, analytics or font host.
- Python 3.11–3.13.
Versions
horo-next-webui X.Y.Z is built from upstream vX.Y.Z or exp-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 for Linux / CPython 3.12, and requirements-X.Y.Z-hashes.txt, the same set for pip install --require-hashes. On a machine with internet access:
pip download horo-next-webui==X.Y.Z -d wheelhouse
Then on the offline machine:
pip install --no-index --find-links wheelhouse horo-next-webui
Security review
Each GitHub release attaches a CycloneDX SBOM, the vulnerability audit and the third-party notices. See the security policy and the reviewer's guide.
License
MIT. Hermes WebUI is copyright its contributors; bundled front-end libraries carry their own licenses, in THIRD_PARTY_LICENSES inside the wheel. KaTeX's fonts are OFL-1.1.
Metadata
Release files for horo-next-webui 0.52.544
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_webui-0.52.544-py3-none-any.whl | Python 3 | none | any | Details for horo_next_webui-0.52.544-py3-none-any.whl |
Release files / horo_next_webui-0.52.544-py3-none-any.whl
| Download URL | horo_next_webui-0.52.544-py3-none-any.whl |
|---|---|
| Size | 6.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3681bf664d3fa150bbe9c3cc9c178a733a92798272f32180b67b8a8e50c82c8
|
|
BLAKE2b-256 checksum How to use checksums |
415d25cf479c26bb36a64a4bed3f1f25c71432cd54230d48cadb1d4fc065ad0c
|
| 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 31, 2026.
Transparency logSecurity for horo-next-webui 0.52.544
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_webui-0.52.544-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 31, 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.