hermes-agent/tests/test_packaging_metadata.py
ethernet d84e11af4d
rip out brew + pip/PyPI wheel support (#68217)
Removes Homebrew and PyPI wheel/sdist as Hermes distribution paths while
preserving the supported source, Docker, and Nix workflows.

Changes:
- Removes the Homebrew formula, PyPI publish workflow, sdist manifest
  (MANIFEST.in), and wheel/sdist release-attachment logic from scripts/release.py.
- Keeps setuptools metadata and entry points required by editable installs
  and Docker/Nix builds, but adds a setup.py guard that rejects wheel/sdist
  builds outside a sealed Nix derivation (HERMES_NIX_BUILD=1).
- Removes pip/Homebrew install detection, PyPI update checks, the pip
  self-update path, the deprecation-banner state, the postinstall subcommand,
  wheel data-directory fallbacks in agent/i18n.py and hermes_constants.py,
  and the ACP Registry manifest/version-lockstep release logic.
- Adds /nix/store/ path detection so `nix run` / `nix profile install`
  installs (which don't set HERMES_MANAGED) are correctly identified as
  "nix" rather than falling through to "git"/"unknown".
- Retired install-method values ("pip", "homebrew") in existing
  .install_method stamps (both code-scoped and home-scoped) are ignored by
  the allowlist reader and fall through to "unknown" instead of resurrecting
  a retired enum value.
- Updates Nix packaging to ship bare runtime data (locales, optional-mcps)
  through store symlinks and wrapper env vars instead of wheel data-files.
- Removes the ACP Registry manifest/icon and their version-lockstep tests.
- Deletes or rewrites packaging, pip-update, Homebrew, and ACP Registry
  tests; adds parametrized coverage for the packaging build guard covering
  BOTH sdist and wheel paths (the guards live in separate cmdclass entries
  — a passing sdist test proves nothing about the wheel path).
- Updates installation/platform documentation and related user-facing copy.
- Adjusts the supply-chain scan so deleted install-hook files do not trigger
  a finding, while additions or modifications still require the existing
  ci-reviewed label gate.

Supported installation paths (unchanged):
- git installer (install.sh)
- Docker
- Nix/NixOS
- editable development installs (uv sync, uv pip install -e ., pip install -e .)
2026-07-22 16:51:01 -04:00

344 lines
14 KiB
Python

import ast
import re
import tomllib
from pathlib import Path
import pytest
REPO_ROOT = Path(__file__).resolve().parents[1]
def _distribution_name(requirement: str) -> str:
"""Extract the PEP 508 distribution name from a requirement string.
Robust to markers (``; python_version < '3.12'``), direct references
(``name @ https://...``), extras (``name[extra]``) and every version
operator (``==``, ``>=``, ``<=``, ``~=``, ``!=``, ``<``, ``>``), so a
future dep declared with any valid specifier shape doesn't silently
mis-parse here.
"""
spec = requirement.split(";", 1)[0] # drop environment markers
spec = spec.split("@", 1)[0] # drop direct-reference URLs
spec = spec.split("[", 1)[0] # drop extras
spec = re.split(r"[=<>!~]", spec, maxsplit=1)[0] # drop any version operator
return spec.strip().lower()
def test_packaging_declared_as_core_dependency():
"""Regression for #40503.
``packaging`` is imported directly on three production paths
(plugins/memory/hindsight/__init__.py, tools/lazy_deps.py,
hermes_cli/main.py) yet was undeclared, so it only reached users
transitively. The slim Docker image shipped without it, silently
disabling Hindsight append-mode and version-constraint checks. It must
be a declared core dependency so it installs everywhere and the
update-repair step (``_verify_core_dependencies_installed``) guards it.
"""
data = tomllib.loads((REPO_ROOT / "pyproject.toml").read_text(encoding="utf-8"))
core = data["project"]["dependencies"]
names = {_distribution_name(dep) for dep in core}
assert "packaging" in names, (
"packaging is imported on production paths (hindsight version compare, "
"lazy_deps version constraints, requirement parsing) and must be a "
"declared core dependency, not a transitive — see #40503"
)
def test_faster_whisper_is_not_a_base_dependency():
data = tomllib.loads((REPO_ROOT / "pyproject.toml").read_text(encoding="utf-8"))
deps = data["project"]["dependencies"]
assert not any(dep.startswith("faster-whisper") for dep in deps)
voice_extra = data["project"]["optional-dependencies"]["voice"]
assert any(dep.startswith("faster-whisper") for dep in voice_extra)
# Minimum non-vulnerable Starlette: CVE-2026-48710 ("BadHost") was fixed in
# 1.0.1. Anything below that lets a malformed Host header desync
# ``request.url.path`` from the dispatched ASGI path, bypassing path-based
# authz in middleware/endpoints that gate on ``request.url``. Starlette is a
# transitive dep (fastapi in [web]; sse-starlette/mcp in [mcp]/[computer-use]/
# [dev]) so we pin it directly in every extra that exposes a server surface and
# enforce the floor in both pyproject and the committed lockfile.
_STARLETTE_CVE_FLOOR = (1, 0, 1)
def _version_tuple(spec: str) -> tuple[int, ...]:
# "1.0.1" -> (1, 0, 1); tolerant of pre/post suffixes by truncating.
head = spec.split("+", 1)[0]
parts = []
for chunk in head.split("."):
digits = "".join(ch for ch in chunk if ch.isdigit())
if not digits:
break
parts.append(int(digits))
return tuple(parts)
def test_starlette_pinned_above_cve_2026_48710_floor_in_pyproject():
"""Every extra that declares Starlette must pin a patched (>=1.0.1) version.
Regression guard for #35067 / CVE-2026-48710. A future edit that drops the
pin (re-exposing the unbounded transitive ``starlette>=0.27`` from mcp /
``>=0.40.0`` from fastapi) or pins a pre-1.0.1 version fails here instead of
shipping a Host-header auth-bypass to dashboard / MCP-HTTP users.
"""
data = tomllib.loads((REPO_ROOT / "pyproject.toml").read_text(encoding="utf-8"))
extras = data["project"]["optional-dependencies"]
found = {}
for extra, specs in extras.items():
for spec in specs:
name = spec.split("==", 1)[0].split(">", 1)[0].split("<", 1)[0].split("[", 1)[0].strip()
if name.lower() == "starlette":
assert "==" in spec, f"[{extra}] must exact-pin starlette, got {spec!r}"
ver = spec.split("==", 1)[1].split(";", 1)[0].strip()
found[extra] = ver
# The four server-surface extras must each carry the direct pin.
for extra in ("web", "mcp", "computer-use", "dev"):
assert extra in found, (
f"[{extra}] no longer pins starlette directly — CVE-2026-48710 "
f"regression risk (mcp/fastapi pull it transitively with no upper bound)"
)
for extra, ver in found.items():
assert _version_tuple(ver) >= _STARLETTE_CVE_FLOOR, (
f"[{extra}] pins starlette=={ver}, below the CVE-2026-48710 fix "
f"floor {'.'.join(map(str, _STARLETTE_CVE_FLOOR))}"
)
def test_locked_starlette_is_not_vulnerable_to_cve_2026_48710():
"""The committed uv.lock must resolve starlette to a patched version.
pyproject pins protect the declared extras, but the lockfile is what
hash-verified installs (``uv sync --locked``) actually pull. Assert the
resolved version is >= the CVE-2026-48710 fix floor so a stale-lock
regression can't ship a vulnerable Starlette to users.
"""
lock = (REPO_ROOT / "uv.lock").read_text(encoding="utf-8")
versions = []
in_starlette = False
for line in lock.splitlines():
if line.startswith("[[package]]"):
in_starlette = False
elif line.strip() == 'name = "starlette"':
in_starlette = True
elif in_starlette and line.startswith("version = "):
versions.append(line.split("=", 1)[1].strip().strip('"'))
in_starlette = False
assert versions, "starlette not found in uv.lock"
for ver in versions:
assert _version_tuple(ver) >= _STARLETTE_CVE_FLOOR, (
f"uv.lock resolves starlette=={ver}, below the CVE-2026-48710 fix "
f"floor {'.'.join(map(str, _STARLETTE_CVE_FLOOR))} — regenerate the "
f"lockfile after bumping the pin"
)
# ---------------------------------------------------------------------------
# Dependency-pin consistency: pyproject extras <-> tools/lazy_deps.py
#
# The same package is exact-pinned in two hand-maintained places: the
# [project.optional-dependencies] extras in pyproject.toml and the LAZY_DEPS
# allowlist in tools/lazy_deps.py (the lazy-install path deliberately mirrors
# the extras — see the comments on LAZY_DEPS: "match the corresponding extra
# in pyproject.toml ... update both this map AND the corresponding extra").
#
# They have silently drifted more than once: the aiohttp Slack pin (3.13.3 in
# the extras vs 3.13.4 in lazy_deps) and the anthropic pin (0.86.0 vs 0.87.0).
# The version a user ends up with then depends on whether the backend was
# installed eagerly (extra) or lazily (lazy_deps) — and for a CVE bump applied
# to only one side, that divergence is a latent security regression. These two
# tests assert the documented contract: the two sources agree, in lockstep.
# ---------------------------------------------------------------------------
# Matches "name==version" and "name[extra]==version", ignoring any trailing
# environment marker / comment. Only exact pins are collected; ranged specs
# (">=", "<") can't be compared for equality and are skipped.
_PIN_RE = re.compile(
r"^\s*([A-Za-z0-9][A-Za-z0-9._-]*)\s*(?:\[[^\]]*\])?\s*==\s*([^\s;,#]+)"
)
def _canonical(name: str) -> str:
# PEP 503 normalization so e.g. discord.py / discord-py compare equal.
return re.sub(r"[-_.]+", "-", name).lower()
def _pins_from_specs(specs):
"""Map canonical package name -> set of exact-pinned versions seen."""
pins: dict[str, set[str]] = {}
for spec in specs:
m = _PIN_RE.match(spec)
if not m:
continue
pins.setdefault(_canonical(m.group(1)), set()).add(m.group(2))
return pins
def _pyproject_pinned_specs():
data = tomllib.loads((REPO_ROOT / "pyproject.toml").read_text(encoding="utf-8"))
specs = list(data["project"].get("dependencies", []))
for extra in data["project"].get("optional-dependencies", {}).values():
specs.extend(extra)
return specs
def _lazy_deps_pinned_specs():
"""Extract every string literal inside the LAZY_DEPS dict via AST.
Parsing rather than importing keeps this test free of
tools/lazy_deps.py's runtime imports and side effects.
"""
src = (REPO_ROOT / "tools" / "lazy_deps.py").read_text(encoding="utf-8")
tree = ast.parse(src)
specs: list[str] = []
for node in ast.walk(tree):
if isinstance(node, ast.Assign):
targets = node.targets
elif isinstance(node, ast.AnnAssign):
targets = [node.target]
else:
continue
if not any(isinstance(t, ast.Name) and t.id == "LAZY_DEPS" for t in targets):
continue
for sub in ast.walk(node.value):
if isinstance(sub, ast.Constant) and isinstance(sub.value, str):
specs.append(sub.value)
assert specs, "could not extract specs from LAZY_DEPS — the AST parser drifted"
return specs
def test_pyproject_pins_are_internally_consistent():
"""No package may be exact-pinned to two different versions in pyproject.
A package legitimately appearing in several extras (e.g. aiohttp in
messaging/slack/homeassistant/sms) must use the SAME version everywhere.
"""
pins = _pins_from_specs(_pyproject_pinned_specs())
conflicts = {name: sorted(v) for name, v in pins.items() if len(v) > 1}
assert not conflicts, (
"pyproject.toml exact-pins the same package to different versions "
"across [project.dependencies] / extras: " + str(conflicts)
)
def test_pyproject_and_lazy_deps_pins_agree():
"""Every package pinned in BOTH places must use the same version.
Regression guard for the aiohttp / anthropic extras-vs-lazy drift:
tools/lazy_deps.py mirrors the pyproject extras, so a CVE bump applied to
one and not the other leaves users on a vulnerable version depending on
the install path. Bump both in lockstep.
"""
py = _pins_from_specs(_pyproject_pinned_specs())
lazy = _pins_from_specs(_lazy_deps_pinned_specs())
mismatches = [
f"{name}: pyproject={sorted(py[name])} lazy_deps={sorted(lazy[name])}"
for name in sorted(set(py) & set(lazy))
if py[name] != lazy[name]
]
assert not mismatches, (
"pyproject.toml extras and tools/lazy_deps.py disagree on the pinned "
"version of the same package — bump both in lockstep:\n "
+ "\n ".join(mismatches)
)
def _lazy_deps_by_feature():
"""Parse LAZY_DEPS into {feature_name: [spec, ...]} via AST.
Same parse-don't-import rationale as _lazy_deps_pinned_specs, but keeps the
feature -> specs grouping so per-feature coverage can be asserted.
"""
src = (REPO_ROOT / "tools" / "lazy_deps.py").read_text(encoding="utf-8")
tree = ast.parse(src)
for node in ast.walk(tree):
targets = (
node.targets if isinstance(node, ast.Assign)
else [node.target] if isinstance(node, ast.AnnAssign)
else []
)
if not any(isinstance(t, ast.Name) and t.id == "LAZY_DEPS" for t in targets):
continue
if not isinstance(node.value, ast.Dict):
continue
by_feature: dict[str, list[str]] = {}
for key, value in zip(node.value.keys, node.value.values):
if not (isinstance(key, ast.Constant) and isinstance(key.value, str)):
continue
by_feature[key.value] = [
sub.value
for sub in ast.walk(value)
if isinstance(sub, ast.Constant) and isinstance(sub.value, str)
]
assert by_feature, "could not extract features from LAZY_DEPS — AST parser drifted"
return by_feature
raise AssertionError("LAZY_DEPS dict literal not found in tools/lazy_deps.py")
# Security-critical packages whose patched floor must be enforced on EVERY
# install path, eager and lazy. test_pyproject_and_lazy_deps_pins_agree only
# fires when a package is pinned in BOTH sources, so it cannot catch a lazy
# feature that omits the pin entirely — the exact gap that left platform.slack
# carrying aiohttp==3.14.0 while platform.discord (whose discord.py dep pulls
# aiohttp transitively as its HTTP backbone) shipped without it, so the lazy
# Discord path could keep an already-installed vulnerable aiohttp. A fully
# general "no mirrored feature drops a pin" check is impossible statically
# (it can't see transitive deps), so this is the explicit coverage contract:
# each security package -> the lazy features that bundle an SDK pulling it and
# must therefore carry the same pin as the pyproject extra.
_REQUIRED_SECURITY_PINS = {
# Every lazy messaging feature whose SDK pulls aiohttp transitively must
# carry the patched floor directly: discord.py (aiohttp<4), slack-bolt,
# mautrix/aiohttp-socks (aiohttp<4 / >=3.10), and microsoft-teams-apps —
# none of those upper/lower bounds excludes a vulnerable already-installed
# aiohttp, so the lazy path would not upgrade it without an explicit pin.
"aiohttp": {
"platform.discord",
"platform.slack",
"platform.matrix",
"platform.teams",
},
}
def test_security_pins_present_in_mirrored_lazy_features():
"""Curated security pins must be present (not just version-consistent) in
every lazy feature that bundles an SDK pulling that package transitively.
"""
py = _pins_from_specs(_pyproject_pinned_specs())
by_feature = _lazy_deps_by_feature()
problems = []
for pkg, features in _REQUIRED_SECURITY_PINS.items():
canon = _canonical(pkg)
expected = py.get(canon)
assert expected, (
f"{pkg} is listed in _REQUIRED_SECURITY_PINS but is not exact-pinned "
f"in pyproject.toml — update the map or the pin."
)
for feature in sorted(features):
specs = by_feature.get(feature)
assert specs is not None, (
f"lazy feature {feature!r} named in _REQUIRED_SECURITY_PINS no "
f"longer exists in LAZY_DEPS — update the map."
)
got = _pins_from_specs(specs).get(canon)
if got != expected:
problems.append(
f"{feature}: {pkg}="
f"{sorted(got) if got else 'MISSING'}, expected {sorted(expected)}"
)
assert not problems, (
"a lazy feature is missing a security pin it must mirror from the "
"pyproject extras — the lazy install path would not enforce the "
"CVE-patched floor:\n " + "\n ".join(problems)
)