calfkit-tools 0.1.0__tar.gz

calfkit_tools-0.1.0/.gitignore

@@ -0,0 +1,218 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+.vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

calfkit_tools-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

calfkit_tools-0.1.0/PKG-INFO

@@ -0,0 +1,112 @@
+Metadata-Version: 2.4
+Name: calfkit-tools
+Version: 0.1.0
+Summary: Vendored agent tools for the calfkit SDK: hermes shell/files/web/todo and an SSRF-safe web_fetch, each deployable as a calfkit tool node.
+Project-URL: Homepage, https://github.com/calf-ai/calfkit-peripherals
+Project-URL: Repository, https://github.com/calf-ai/calfkit-peripherals
+Project-URL: Issues, https://github.com/calf-ai/calfkit-peripherals/issues
+Author: calf-ai
+License-Expression: Apache-2.0 AND MIT
+License-File: LICENSE
+License-File: THIRD_PARTY_NOTICES.md
+License-File: vendor/hermes/LICENSE
+License-File: vendor/web_fetch/LICENSE
+Keywords: agent,agent-tools,calfkit,kafka,llm,tools
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.11
+Requires-Dist: calfkit<0.10,>=0.9.0
+Requires-Dist: ddgs
+Requires-Dist: httpx>=0.27
+Requires-Dist: markdownify>=1.2
+Requires-Dist: psutil
+Requires-Dist: ptyprocess; sys_platform != 'win32'
+Requires-Dist: pydantic
+Requires-Dist: pyyaml
+Requires-Dist: requests
+Requires-Dist: typing-extensions
+Provides-Extra: all
+Requires-Dist: daytona-sdk; extra == 'all'
+Requires-Dist: docker; extra == 'all'
+Requires-Dist: modal; extra == 'all'
+Provides-Extra: shell-daytona
+Requires-Dist: daytona-sdk; extra == 'shell-daytona'
+Provides-Extra: shell-docker
+Requires-Dist: docker; extra == 'shell-docker'
+Provides-Extra: shell-modal
+Requires-Dist: modal; extra == 'shell-modal'
+Description-Content-Type: text/markdown
+
+# 🐮 calfkit-tools
+
+A single distribution where **calfkit** vendors agent tools ported from many upstream
+open-source codebases into one place.
+
+calfkit's tool interface is **Kafka-based** (language-agnostic): a "node tool" is a process
+that consumes a request topic and produces a reply. This repo packages those tools as one
+installable distribution, **`calfkit-tools`** — organised internally by the upstream source
+each tool was vendored from, each a subpackage exposing its tools over the calfkit Kafka
+contract.
+
+## Layout
+
+- `src/calfkit_tools/<source>/` — one subpackage per upstream source (e.g. `hermes`,
+  `web_fetch`); its tool nodes live under `<source>/node/`.
+- `vendor/<source>/` — provenance only (`LICENSE`, `METADATA.yaml`, `NODE.md`, `README.md`,
+  `patches/`). Never on `sys.path`, never in the wheel.
+- `vendor/_template/` — copy this to start a new source.
+- `tests/<source>/` — per-source test suites.
+- `pyproject.toml` — the single `calfkit-tools` distribution (deps + extras).
+- `docs/project-structure.md` — **start here** to add a source.
+- `docs/reference/tool-contracts.md` — roll-up of every tool node's interface
+  contract (params, deps/resource wiring, env config, reply shapes); each
+  source's `vendor/<source>/NODE.md` stays authoritative.
+- `docs/design/` — per-tool design docs (e.g. the hermes-agent shell+file port).
+- `docs/tools-research/` — the upstream survey that informed which tools to vendor.
+- `THIRD_PARTY_NOTICES.md` — aggregated attribution index (per-source `vendor/<source>/LICENSE`
+  + `METADATA.yaml` are authoritative).
+
+## Install
+
+One distribution covers every default tool path:
+
+```bash
+pip install calfkit-tools          # or: uv add calfkit-tools
+```
+
+The base install runs all tools with their default backends. Three **opt-in** extras enable
+remote shell-execution backends only (the default local backend needs none of them):
+
+```bash
+pip install "calfkit-tools[shell-docker]"   # docker backend
+pip install "calfkit-tools[shell-modal]"    # modal backend
+pip install "calfkit-tools[shell-daytona]"  # daytona backend
+pip install "calfkit-tools[all]"            # all three
+```
+
+## Adding a source
+
+Add code under `src/calfkit_tools/<source>/`, provenance under `vendor/<source>/`, tests under
+`tests/<source>/`, and any new deps/extras to the root `pyproject.toml`. Follow
+[`docs/project-structure.md`](docs/project-structure.md). Vendor **by source** (license-first,
+per the `open-source-vendoring-best-practices` conventions), expose **by tool**, and keep
+upstream code import-rewritten under `_vendor/`.
+
+## Status
+
+**Stage D landed:** all eleven vendored tools are deployable calfkit tool nodes
+(calfkit ≥ 0.9.0, 1:1 tool→node, in-memory multitenancy keyed per calling agent
+— ADR-0004). Import-and-deploy:
+
+```python
+from calfkit_tools.hermes.node import HERMES_NODES          # terminal, process, files, todo, web, execute_code
+from calfkit_tools.web_fetch.node import web_fetch
+```
+
+See [`docs/design/node-port.md`](docs/design/node-port.md) and each source's
+`vendor/<source>/NODE.md` for contracts, wiring, and the trust model. Durable state and
+security hardening remain deferred.

calfkit_tools-0.1.0/README.md

@@ -0,0 +1,69 @@
+# 🐮 calfkit-tools
+
+A single distribution where **calfkit** vendors agent tools ported from many upstream
+open-source codebases into one place.
+
+calfkit's tool interface is **Kafka-based** (language-agnostic): a "node tool" is a process
+that consumes a request topic and produces a reply. This repo packages those tools as one
+installable distribution, **`calfkit-tools`** — organised internally by the upstream source
+each tool was vendored from, each a subpackage exposing its tools over the calfkit Kafka
+contract.
+
+## Layout
+
+- `src/calfkit_tools/<source>/` — one subpackage per upstream source (e.g. `hermes`,
+  `web_fetch`); its tool nodes live under `<source>/node/`.
+- `vendor/<source>/` — provenance only (`LICENSE`, `METADATA.yaml`, `NODE.md`, `README.md`,
+  `patches/`). Never on `sys.path`, never in the wheel.
+- `vendor/_template/` — copy this to start a new source.
+- `tests/<source>/` — per-source test suites.
+- `pyproject.toml` — the single `calfkit-tools` distribution (deps + extras).
+- `docs/project-structure.md` — **start here** to add a source.
+- `docs/reference/tool-contracts.md` — roll-up of every tool node's interface
+  contract (params, deps/resource wiring, env config, reply shapes); each
+  source's `vendor/<source>/NODE.md` stays authoritative.
+- `docs/design/` — per-tool design docs (e.g. the hermes-agent shell+file port).
+- `docs/tools-research/` — the upstream survey that informed which tools to vendor.
+- `THIRD_PARTY_NOTICES.md` — aggregated attribution index (per-source `vendor/<source>/LICENSE`
+  + `METADATA.yaml` are authoritative).
+
+## Install
+
+One distribution covers every default tool path:
+
+```bash
+pip install calfkit-tools          # or: uv add calfkit-tools
+```
+
+The base install runs all tools with their default backends. Three **opt-in** extras enable
+remote shell-execution backends only (the default local backend needs none of them):
+
+```bash
+pip install "calfkit-tools[shell-docker]"   # docker backend
+pip install "calfkit-tools[shell-modal]"    # modal backend
+pip install "calfkit-tools[shell-daytona]"  # daytona backend
+pip install "calfkit-tools[all]"            # all three
+```
+
+## Adding a source
+
+Add code under `src/calfkit_tools/<source>/`, provenance under `vendor/<source>/`, tests under
+`tests/<source>/`, and any new deps/extras to the root `pyproject.toml`. Follow
+[`docs/project-structure.md`](docs/project-structure.md). Vendor **by source** (license-first,
+per the `open-source-vendoring-best-practices` conventions), expose **by tool**, and keep
+upstream code import-rewritten under `_vendor/`.
+
+## Status
+
+**Stage D landed:** all eleven vendored tools are deployable calfkit tool nodes
+(calfkit ≥ 0.9.0, 1:1 tool→node, in-memory multitenancy keyed per calling agent
+— ADR-0004). Import-and-deploy:
+
+```python
+from calfkit_tools.hermes.node import HERMES_NODES          # terminal, process, files, todo, web, execute_code
+from calfkit_tools.web_fetch.node import web_fetch
+```
+
+See [`docs/design/node-port.md`](docs/design/node-port.md) and each source's
+`vendor/<source>/NODE.md` for contracts, wiring, and the trust model. Durable state and
+security hardening remain deferred.

calfkit_tools-0.1.0/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,43 @@
+# Third-Party Notices
+
+`calfkit-tools` vendors source from external open-source projects. Each vendored source's
+provenance lives under `vendor/<source>/` and carries its own **authoritative** `LICENSE`
+(verbatim upstream) and `METADATA.yaml` (provenance: repo, commit, license, files, local
+modifications); the vendored code itself lives under `src/calfkit_tools/<source>/_vendor/`.
+This file is the aggregated index across sources.
+
+## Conventions
+
+See `docs/project-structure.md` and the `open-source-vendoring-best-practices` skill.
+
+- Vendor **by source**, with the license **checked and classified before** copying.
+- **Permissive licenses only** (MIT / BSD / ISC / Apache-2.0 / Unlicense / 0BSD / CC0).
+  Weak/strong copyleft, "no license", and source-available/restricted licenses are a
+  **stop-and-flag** — do not copy without an explicit decision.
+- Preserve all upstream copyright/license headers. Record **secondary-origin**
+  attributions when an upstream itself ported code from a third project.
+- Note local modifications (the mechanical import-rewrite and any `patches/`).
+
+## Sources
+
+### hermes  (MIT)
+- Upstream: https://github.com/NousResearch/hermes-agent @ `5a36f76a00cc448948856a5c1b52710aafec264e`, retrieved 2026-06-07
+- License: MIT — © 2025 Nous Research  (full text: `vendor/hermes/LICENSE`)
+- Vendored under: `src/calfkit_tools/hermes/_vendor/`  (provenance: `vendor/hermes/`)
+- Tools: shell (terminal, process, execute_code), files (read/write/patch/search), web_search + web_extract (provider system: ddgs / brave-free / searxng / tavily), todo (per-session task list)
+- Secondary origins: opencode (MIT), nearai/ironclaw (elect-MIT), free-code (MIT) — see `vendor/hermes/METADATA.yaml`
+
+### web_fetch  (MIT)
+- Upstream: https://github.com/pydantic/pydantic-ai @ `1b42945de65b2816fed3cffa371671a2ac759241` (tag `v1.106.0`), retrieved 2026-06-08
+- License: MIT — © Pydantic Services Inc.  (full text: `vendor/web_fetch/LICENSE`)
+- Vendored under: `src/calfkit_tools/web_fetch/_vendor/`  (provenance: `vendor/web_fetch/`)
+- Tools: web_fetch (SSRF-safe URL → markdown / neutral binary)
+- Secondary origins: none found (H3 verified — `_ssrf.py` IP/cloud-metadata tables are independently authored from primary RFCs; see `vendor/web_fetch/METADATA.yaml`)
+
+<!-- Per-source entry template:
+### <source-name>  (<SPDX>)
+- Upstream: <repo URL> @ <commit SHA>, retrieved <YYYY-MM-DD>
+- License: <SPDX> — © <year> <holder>  (full text: vendor/<source>/LICENSE)
+- Vendored under: src/calfkit_tools/<source>/_vendor/  (provenance: vendor/<source>/)
+- Secondary origins (if any): <project> (<SPDX>) — <files>
+-->