SchemaLibrary

LiteLLMGuardSchemas

Schema fragments for the Components that run the LiteLLM proxy behind the request guard of the LiteLLMGuard#/artifacts/RequestGuard bundle. RequestGuardInfra declares admitted_request_fields, the infra key a Release names further request fields in for the guard to forward. It is declared here once for every such Component, so what the key admits, and what it cannot re-open, is stated in one place wherever the guard runs.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:ad6a090473853f61368c4cf1389e08868aa3f11243ba688da6a857ee0a9ff0d3
Published
2026-11-10T10:29:09Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:6b8be8ec6581d95a1db29ed22dbe52d4e4398d3891a7c4b46686ba9a9b3b4f4a

Reference at this version

oci://hub.aggrega.ai/schemalibrary/litellmguardschemas:1.0.0

RequestGuardInfra

NameTypeDefaultRequiredDescription
admitted_request_fieldsarray—noRequest fields the proxy forwards from a caller on top of the ones it already forwards for the route. The proxy forwards only the fields LiteLLM itself declares for each route and refuses the rest, so a caller cannot change where a request is sent or with which credential; a Release whose callers must send a further field names it here, and it is admitted on every route; a Feature attached to the proxy can still refuse it, as core/data-masking refuses every field its masking does not reach, an admitted one included. It cannot re-open a refused field — naming one the proxy refuses (a credential, an endpoint, or a routing field such as model_list or fallbacks) halts the build, because those are what the refusal exists to stop. Omitted, the proxy admits nothing beyond each route's own fields.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

This entity uses nothing in the catalog.

Used by

SchemaLibrary concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy