securevector-sdk-hermes 1.0.0__tar.gz

securevector_sdk_hermes-1.0.0/CHANGELOG.md

@@ -0,0 +1,50 @@
+# Changelog
+
+All notable changes to `securevector-sdk-hermes` are documented here.
+This project adheres to [Semantic Versioning](https://semver.org/).
+
+## [1.0.0]
+
+### Added
+- Initial Hermes (NousResearch `hermes-agent`) adapter — release unit δ of the
+  `active-guard-plugin` bundle, story #183.
+- **Zero-config Hermes plugin** via the `hermes_agent.plugins` entry point:
+  the Hermes plugin manager auto-loads the guard in every mode (interactive
+  CLI, gateway, ACP). `pre_tool_call` enforces via Hermes's documented block
+  directive (`{"action": "block", "message": ...}`) with the
+  `SecureVector Guard:` branded reason; `post_tool_call` scans tool results.
+  Runs the three controls on every tool call:
+  - **(a)** tool-call permission resolution (synced → override → essential → default-allow),
+  - **(b)** secret / data-leak detection on tool input and output,
+  - **(c)** threat detection on tool input and output.
+- `install(mode=...)` for programmatic embeddings — wraps
+  `tools.registry.dispatch`, the choke point all Hermes execution paths funnel
+  through (deliberately NOT `model_tools.handle_function_call`, which
+  `run_agent` re-imports by reference). `import securevector_sdk_hermes.auto`
+  calls it with env-derived mode.
+- **MCP-aware tool-id candidates**: Hermes registers MCP tools as
+  `mcp_<server>_<tool>` (hyphens/dots sanitized to underscores — lossy), so
+  permission resolution matches the raw Hermes name plus every
+  `<server>:<tool>` split, tier precedence first.
+- `HERMES_BUILTINS` — empirical built-in inventory extracted from the
+  hermes-agent 0.18.0 sdist (69 registry tools + 3 Tool-Search bridge tools +
+  bundled plugin tools), with a drift test that compares against a live
+  hermes-agent install when importable.
+- `observe` (fail-open, default) and `enforce` (fail-closed) modes; one-line
+  cold-install notice when the app is unreachable in observe mode.
+- Audit forwarding to the local app's tamper-evident chain with
+  `runtime_kind="hermes"` attribution, keyed by Hermes `session_id` /
+  `tool_call_id`.
+- `/analyze` requests send the correct `direction` field (`outgoing` for tool
+  input, `incoming` for tool output) — fixes the `mode`-field drift present in
+  the sibling SDKs, so tool-output scans actually run the IDPI rule pack.
+- Base URL honors the unified `SECUREVECTOR_ENGINE_ENDPOINT` (with legacy
+  `SECUREVECTOR_SDK_APP_URL` fallback) and forwards an optional
+  `SECUREVECTOR_API_KEY` as `Authorization: Bearer` for remote, token-gated
+  deployments.
+- Version pin `hermes-agent>=0.18,<0.19` — the attach points are re-verified
+  before every pin raise.
+- Harness-tailored [PRIVACY.md](PRIVACY.md); Apache-2.0 LICENSE + NOTICE with
+  Nous Research trademark disclaimer.
+- CI + Test PyPI (develop) / PyPI (main release) publishing via OIDC trusted
+  publishing, mirroring the sibling framework SDKs.

securevector_sdk_hermes-1.0.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

securevector_sdk_hermes-1.0.0/MANIFEST.in

@@ -0,0 +1,7 @@
+# Ship the compliance/privacy docs in the source distribution. Story #183
+# requires the harness-tailored PRIVACY.md in the shipped artifact; LICENSE and
+# NOTICE are already picked up as license-files, but PRIVACY.md and the
+# CHANGELOG are not, so include them explicitly.
+include PRIVACY.md
+include CHANGELOG.md
+include NOTICE

securevector_sdk_hermes-1.0.0/NOTICE

@@ -0,0 +1,16 @@
+SecureVector SDK for Hermes
+Copyright (c) SecureVector
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+This software integrates with the Hermes agent framework via its public
+plugin API (the `hermes_agent.plugins` entry-point group and its documented
+`pre_tool_call` / `post_tool_call` hooks). "Hermes" and "Nous Research" are
+trademarks of Nous Research. This package is an independent, community
+integration and is not affiliated with, sponsored by, or endorsed by Nous
+Research. The framework name is used only descriptively to identify
+compatibility (nominative fair use).
+
+This package depends on:
+  - securevector-ai-monitor (the local SecureVector app + SDK)
+  - hermes-agent (MIT, (c) 2025 Nous Research)

securevector_sdk_hermes-1.0.0/PKG-INFO

@@ -0,0 +1,155 @@
+Metadata-Version: 2.4
+Name: securevector-sdk-hermes
+Version: 1.0.0
+Summary: SecureVector SDK for Hermes (NousResearch hermes-agent) — brings the local threat monitor's three controls (tool-call permissions, secret/data-leak detection, threat detection) to every Hermes tool call, with tamper-evident audit logging.
+Author: SecureVector
+License: Apache-2.0
+Project-URL: Homepage, https://securevector.io
+Project-URL: Source, https://github.com/Secure-Vector/securevector-sdk-hermes
+Keywords: hermes,hermes-agent,llm,security,ai-agent,audit,compliance,tool-permissions
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: securevector-ai-monitor>=4.7
+Requires-Dist: hermes-agent<0.19,>=0.18
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Dynamic: license-file
+
+# SecureVector SDK for Hermes
+
+[![PyPI](https://img.shields.io/pypi/v/securevector-sdk-hermes)](https://pypi.org/project/securevector-sdk-hermes/)
+[![Downloads](https://img.shields.io/pypi/dm/securevector-sdk-hermes)](https://pypistats.org/packages/securevector-sdk-hermes)
+[![Python](https://img.shields.io/badge/python-3.11%2B-blue)](https://pypi.org/project/securevector-sdk-hermes/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-green)](LICENSE)
+
+> Bring the SecureVector local threat monitor's three controls — **tool-call
+> permissions**, **secret / data-leak detection**, and **threat detection** —
+> to every Hermes (NousResearch `hermes-agent`) tool call, with tamper-evident
+> audit logging. Zero code changes.
+
+```bash
+pip install securevector-sdk-hermes
+```
+
+> 📦 **One install — batteries included.** `pip install securevector-sdk-hermes`
+> **also installs the local SecureVector app** (`securevector-ai-monitor`): the
+> adapter **and** the detection engine + tamper-evident audit chain arrive in a
+> single `pip install`. The SDK is a thin interception layer — **the app must be
+> running locally** (`securevector-app --web`) for it to do anything.
+
+## Quick start
+
+**Zero-config (recommended).** The package registers a Hermes plugin via the
+`hermes_agent.plugins` entry point — the Hermes plugin manager auto-loads it
+on startup in **every mode**: the interactive `hermes` CLI, `hermes gateway`
+(Telegram / Discord / Slack / …), and the ACP/Zed adapter.
+
+```bash
+pip install securevector-sdk-hermes
+hermes                       # that's it — observe mode is on
+
+export SECUREVECTOR_SDK_MODE=enforce   # opt into blocking
+hermes
+```
+
+A denied tool is stopped through Hermes's own `pre_tool_call` block directive —
+the model sees a clean `SecureVector Guard: tool '<name>' blocked — <reason>`
+result. No exceptions, no crashed runs, no fork of Hermes.
+
+**Programmatic / library embeddings** (driving `AIAgent` from your own Python
+process, where the plugin manager never runs):
+
+```python
+from securevector_sdk_hermes import install
+
+install(mode="enforce")   # wraps Hermes's tool-registry dispatch
+```
+
+> Why two paths? The plugin hooks are Hermes's **documented interception
+> surface** and require no code at all. `install()` covers embeddings by
+> wrapping `tools.registry.dispatch` — the single choke point every Hermes
+> execution path (CLI, gateway, ACP, subagents) funnels through.
+
+## What happens on every tool call
+
+Before a tool runs, the SDK:
+
+1. **(a) Permissions** — resolves an allow/block verdict for the tool, using the
+   app's own precedence: cloud-pushed **synced** policy → local **override** →
+   **essential** registry → default-allow. Hermes MCP tools
+   (`mcp_<server>_<tool>`) are matched against the raw Hermes name **and** the
+   cloud `<server>:<tool>` form, so policies authored either way apply.
+2. **(b)+(c) Secret & threat scan** — sends the serialized tool input through the
+   app's `/analyze` pipeline.
+
+After the tool returns, the result is scanned the same way to catch secrets /
+exfiltration in tool output. Every decision is written to the app's audit chain
+tagged `runtime_kind="hermes"`, keyed by Hermes's own `session_id` and
+`tool_call_id`.
+
+This covers all ~70 Hermes built-in tools (`terminal`, `execute_code`,
+`write_file`, `browser_*`, …), every MCP tool, and plugin tools — including in
+gateway/headless contexts where Hermes's built-in dangerous-command approval
+is known to fail open (upstream `hermes-agent` issue #30882): the guard sits
+underneath the approval layer, at the dispatch choke point.
+
+## observe vs enforce
+
+| | local app reachable | local app unreachable |
+|---|---|---|
+| **observe** (default) | log + advisory verdict; tool always runs | tool runs (fail-open, one-line notice) |
+| **enforce** (opt-in) | tool runs only if the verdict ≠ block | **tool denied** (fail-closed) |
+
+Enforce mode prints a one-time disclosure to stderr.
+
+## Configuration
+
+All optional, via env (the plugin path) or `install(...)` kwargs:
+
+| Env var | Default | Meaning |
+|---|---|---|
+| `SECUREVECTOR_ENGINE_ENDPOINT` | `http://127.0.0.1:8741` | local app / engine base URL (unified variable; legacy `SECUREVECTOR_SDK_APP_URL` also honored) |
+| `SECUREVECTOR_SDK_MODE` | `observe` | `observe` or `enforce` |
+| `SECUREVECTOR_SDK_TIMEOUT_MS` | `3000` | per-call verdict timeout |
+| `SECUREVECTOR_SDK_RISK_THRESHOLD` | `70` | risk score that blocks in enforce mode |
+| `SECUREVECTOR_SDK_DISABLED` | _(unset)_ | set truthy to no-op |
+| `SECUREVECTOR_API_KEY` | _(unset)_ | bearer credential for remote, token-gated deployments |
+
+## Version pinning
+
+The guard attaches to Hermes internals (the plugin hook bus and
+`tools.registry`), so the dependency is pinned to the verified minor:
+`hermes-agent>=0.18,<0.19`. Each upstream minor is re-verified against the
+attach points before the pin is raised — see [CHANGELOG](CHANGELOG.md).
+
+## Privacy
+
+Everything runs on loopback; the SDK makes no external network calls. See
+[PRIVACY.md](PRIVACY.md) for the exact read/send surface.
+
+## Compliance
+
+The tool-call-level, attributed, tamper-evident audit trail this produces is
+exactly the **action-layer logging** auditors ask for under **EU AI Act
+Art. 12 / 15**. This SDK produces the local evidence; the cloud governance
+surface turns it into an auditor-ready pack.
+
+## Trademarks
+
+**SecureVector** is the product name of this SDK. **Hermes** and **Nous
+Research** are trademarks of Nous Research. This is an independent, community
+SDK that *integrates with* Hermes via its public plugin API. It is **not
+affiliated with, sponsored by, or endorsed by Nous Research.** The name uses
+"hermes" only descriptively, to identify the framework this package works
+with (nominative fair use).
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

securevector_sdk_hermes-1.0.0/PRIVACY.md

@@ -0,0 +1,96 @@
+# Privacy Policy — SecureVector SDK for Hermes
+
+**Last updated:** 2026-07-01
+**Applies to:** securevector-sdk-hermes v1.0.x
+
+The SecureVector SDK for Hermes runs entirely on your machine, inside the same
+Python process as NousResearch's `hermes-agent`. It observes Hermes tool calls
+through Hermes's public plugin hooks (`pre_tool_call` / `post_tool_call`) — or,
+for library embeddings, a wrap of Hermes's tool-registry dispatch — and posts a
+small payload over **loopback HTTP** to a companion app you installed locally.
+The SDK itself makes no network calls to SecureVector, to Nous Research, or to
+any third party.
+
+What happens to the data *after* it reaches the companion app — local storage,
+optional cloud sync, retention, deletion — is governed by the **companion
+app's** own privacy policy, not this one.
+
+## What the SDK reads
+
+| Surface | What it reads | Where it sends it |
+|---|---|---|
+| `pre_tool_call` hook (or dispatch wrap, pre-execution) | Tool name, serialized tool arguments, Hermes `session_id` / `tool_call_id` / `api_request_id` | Local app: GET `/api/tool-permissions/{essential,overrides,synced-overrides}` (no user data in the GETs), POST `/analyze` (arguments text, capped at 100 KB), POST `/api/tool-permissions/call-audit` (tool id, decision, an args preview truncated to 500 chars) |
+| `post_tool_call` hook (or dispatch wrap, post-execution) | Tool name and the tool's result text | Local app POST `/analyze` (result text, capped at 100 KB); POST `/api/tool-permissions/call-audit` only when a finding is detected |
+
+The SDK never reads Hermes state files, `~/.hermes/` contents, prompts, or
+model responses — only what Hermes passes to the tool-call hooks.
+
+## Where the data goes
+
+Every network-bound surface talks to **loopback HTTP** at
+`http://127.0.0.1:8741` (overridable via `SECUREVECTOR_ENGINE_ENDPOINT`, or
+the legacy `SECUREVECTOR_SDK_APP_URL`). Traffic never leaves your machine
+unless you deliberately point that variable at a remote SecureVector
+deployment you operate (in which case `SECUREVECTOR_API_KEY` is forwarded as
+a bearer credential to that host and nothing else).
+
+The SDK writes no files to disk.
+
+For anything the companion app does with payloads after they arrive (local
+SQLite persistence, optional Cloud Connect, SIEM forwarding, retention
+windows, deletion), see the companion app's privacy documentation:
+<https://github.com/Secure-Vector/securevector-ai-threat-monitor>.
+
+## Client-side redaction before any POST
+
+Before sending an `args_preview` to the audit endpoint, the SDK masks common
+secret shapes (AWS access key IDs, GitHub `ghp_` tokens, `sk-…` API keys,
+labelled `password=` pairs) and truncates to 500 characters. Redaction is
+**best-effort pattern matching, not a cryptographic guarantee** — the
+canonical pattern set lives in `src/securevector_sdk_hermes/core.py`. The
+full argument/result text sent to `/analyze` is redacted and persisted by the
+companion app according to its own policy.
+
+## What the SDK never collects
+
+- **No external telemetry, analytics, or crash reports.**
+- **No data to Nous Research.**
+- **No data to SecureVector's cloud.** The SDK makes no outbound network calls.
+- **No OS identifiers, IP addresses, or third-party account identifiers.**
+  The SDK forwards the Hermes-generated `session_id` / `tool_call_id` to the
+  **local** endpoints for correlation; these identifiers never leave the
+  loopback POSTs.
+
+## Failing open
+
+If the local companion app is unreachable, `observe` mode (the default) lets
+every tool call proceed — the event is dropped, not queued, buffered, or
+retried, and never reaches network. A one-line notice is printed once per
+process. In `enforce` mode an unreachable app blocks tool calls (fail-closed)
+by design; no data is transmitted in either case.
+
+## Disabling the SDK
+
+- `pip uninstall securevector-sdk-hermes`, or
+- set `SECUREVECTOR_SDK_DISABLED=1` to no-op without uninstalling.
+
+Once disabled, no hooks are registered and no POSTs are made.
+
+## Source code & licence
+
+The SDK is **Apache-2.0 licensed** and published at
+<https://github.com/Secure-Vector/securevector-sdk-hermes>. The whole
+interception surface is auditable — `plugin.py` (hooks + dispatch wrap),
+`client.py` (every HTTP call), and `core.py` (decision logic + redactor) — we
+encourage reviewing them before installation.
+
+## Changes to this policy
+
+We may update this policy from time to time. Material changes will bump the
+**Last updated** date and be noted in the [CHANGELOG](./CHANGELOG.md).
+
+## Contact
+
+For privacy questions about the SDK, email **privacy@securevector.io**, or
+open an issue at
+<https://github.com/Secure-Vector/securevector-sdk-hermes/issues>.

securevector_sdk_hermes-1.0.0/README.md

@@ -0,0 +1,131 @@
+# SecureVector SDK for Hermes
+
+[![PyPI](https://img.shields.io/pypi/v/securevector-sdk-hermes)](https://pypi.org/project/securevector-sdk-hermes/)
+[![Downloads](https://img.shields.io/pypi/dm/securevector-sdk-hermes)](https://pypistats.org/packages/securevector-sdk-hermes)
+[![Python](https://img.shields.io/badge/python-3.11%2B-blue)](https://pypi.org/project/securevector-sdk-hermes/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-green)](LICENSE)
+
+> Bring the SecureVector local threat monitor's three controls — **tool-call
+> permissions**, **secret / data-leak detection**, and **threat detection** —
+> to every Hermes (NousResearch `hermes-agent`) tool call, with tamper-evident
+> audit logging. Zero code changes.
+
+```bash
+pip install securevector-sdk-hermes
+```
+
+> 📦 **One install — batteries included.** `pip install securevector-sdk-hermes`
+> **also installs the local SecureVector app** (`securevector-ai-monitor`): the
+> adapter **and** the detection engine + tamper-evident audit chain arrive in a
+> single `pip install`. The SDK is a thin interception layer — **the app must be
+> running locally** (`securevector-app --web`) for it to do anything.
+
+## Quick start
+
+**Zero-config (recommended).** The package registers a Hermes plugin via the
+`hermes_agent.plugins` entry point — the Hermes plugin manager auto-loads it
+on startup in **every mode**: the interactive `hermes` CLI, `hermes gateway`
+(Telegram / Discord / Slack / …), and the ACP/Zed adapter.
+
+```bash
+pip install securevector-sdk-hermes
+hermes                       # that's it — observe mode is on
+
+export SECUREVECTOR_SDK_MODE=enforce   # opt into blocking
+hermes
+```
+
+A denied tool is stopped through Hermes's own `pre_tool_call` block directive —
+the model sees a clean `SecureVector Guard: tool '<name>' blocked — <reason>`
+result. No exceptions, no crashed runs, no fork of Hermes.
+
+**Programmatic / library embeddings** (driving `AIAgent` from your own Python
+process, where the plugin manager never runs):
+
+```python
+from securevector_sdk_hermes import install
+
+install(mode="enforce")   # wraps Hermes's tool-registry dispatch
+```
+
+> Why two paths? The plugin hooks are Hermes's **documented interception
+> surface** and require no code at all. `install()` covers embeddings by
+> wrapping `tools.registry.dispatch` — the single choke point every Hermes
+> execution path (CLI, gateway, ACP, subagents) funnels through.
+
+## What happens on every tool call
+
+Before a tool runs, the SDK:
+
+1. **(a) Permissions** — resolves an allow/block verdict for the tool, using the
+   app's own precedence: cloud-pushed **synced** policy → local **override** →
+   **essential** registry → default-allow. Hermes MCP tools
+   (`mcp_<server>_<tool>`) are matched against the raw Hermes name **and** the
+   cloud `<server>:<tool>` form, so policies authored either way apply.
+2. **(b)+(c) Secret & threat scan** — sends the serialized tool input through the
+   app's `/analyze` pipeline.
+
+After the tool returns, the result is scanned the same way to catch secrets /
+exfiltration in tool output. Every decision is written to the app's audit chain
+tagged `runtime_kind="hermes"`, keyed by Hermes's own `session_id` and
+`tool_call_id`.
+
+This covers all ~70 Hermes built-in tools (`terminal`, `execute_code`,
+`write_file`, `browser_*`, …), every MCP tool, and plugin tools — including in
+gateway/headless contexts where Hermes's built-in dangerous-command approval
+is known to fail open (upstream `hermes-agent` issue #30882): the guard sits
+underneath the approval layer, at the dispatch choke point.
+
+## observe vs enforce
+
+| | local app reachable | local app unreachable |
+|---|---|---|
+| **observe** (default) | log + advisory verdict; tool always runs | tool runs (fail-open, one-line notice) |
+| **enforce** (opt-in) | tool runs only if the verdict ≠ block | **tool denied** (fail-closed) |
+
+Enforce mode prints a one-time disclosure to stderr.
+
+## Configuration
+
+All optional, via env (the plugin path) or `install(...)` kwargs:
+
+| Env var | Default | Meaning |
+|---|---|---|
+| `SECUREVECTOR_ENGINE_ENDPOINT` | `http://127.0.0.1:8741` | local app / engine base URL (unified variable; legacy `SECUREVECTOR_SDK_APP_URL` also honored) |
+| `SECUREVECTOR_SDK_MODE` | `observe` | `observe` or `enforce` |
+| `SECUREVECTOR_SDK_TIMEOUT_MS` | `3000` | per-call verdict timeout |
+| `SECUREVECTOR_SDK_RISK_THRESHOLD` | `70` | risk score that blocks in enforce mode |
+| `SECUREVECTOR_SDK_DISABLED` | _(unset)_ | set truthy to no-op |
+| `SECUREVECTOR_API_KEY` | _(unset)_ | bearer credential for remote, token-gated deployments |
+
+## Version pinning
+
+The guard attaches to Hermes internals (the plugin hook bus and
+`tools.registry`), so the dependency is pinned to the verified minor:
+`hermes-agent>=0.18,<0.19`. Each upstream minor is re-verified against the
+attach points before the pin is raised — see [CHANGELOG](CHANGELOG.md).
+
+## Privacy
+
+Everything runs on loopback; the SDK makes no external network calls. See
+[PRIVACY.md](PRIVACY.md) for the exact read/send surface.
+
+## Compliance
+
+The tool-call-level, attributed, tamper-evident audit trail this produces is
+exactly the **action-layer logging** auditors ask for under **EU AI Act
+Art. 12 / 15**. This SDK produces the local evidence; the cloud governance
+surface turns it into an auditor-ready pack.
+
+## Trademarks
+
+**SecureVector** is the product name of this SDK. **Hermes** and **Nous
+Research** are trademarks of Nous Research. This is an independent, community
+SDK that *integrates with* Hermes via its public plugin API. It is **not
+affiliated with, sponsored by, or endorsed by Nous Research.** The name uses
+"hermes" only descriptively, to identify the framework this package works
+with (nominative fair use).
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).