Skip to content

v0.2.0 — security hardening

Choose a tag to compare

View all tags
@breman27 breman27 released this 11 Jul 00:39
v0.2.0
f98b73f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

agent-catalog v0.2.0 — technical preview

A security-hardening release. Published via npm trusted publishing (OIDC) with provenance.

Security

  • Card-fetch path/port hardening. The agentcatalog.io/a2a-path Service annotation is untrusted (anyone who can label a discoverable Service) and flowed into a privileged kube-apiserver service-proxy request. It's now sanitized — schemes, queries, fragments, %-encoding, and .. traversal are rejected and fall back to the well-known card paths; agentcatalog.io/a2a-port is clamped to 1–65535.
  • Response size caps. Card bodies over 1 MiB and oversized LiteLLM usage responses are rejected before parsing — bounding parse cost and stored-entity size against a hostile or broken endpoint.
  • Gateway key protection. The LiteLLM spend key is never sent over a non-HTTPS, non-loopback baseUrl (fail closed); HTTP remains allowed only for loopback.

Internal

  • Mocked-kube-client tests for the four entity providers and the first frontend tests (toRow + AgentInfoCard). 52 → 92 tests.
  • Demo: DEMO_CLUSTER_CONTEXTS to scan multiple clusters (demo tooling only).

Full notes: CHANGELOG.md.

Assets 2
Loading