Component
core/security/presidio-anonymizer
The Presidio anonymizer: a service that replaces spans of a text it is told about. A caller posts a text together with the list of spans to act on — each with its position and its entity type, in the shape the Presidio analyzer reports — and the service answers with the rewritten text and what it did to each span. Each entity type is handled by the operator the request names for it: replaced by a given value, removed, overwritten character by character, hashed or encrypted; with none named, every span is replaced by its entity type in angle brackets, such as <PERSON>. It can also reverse its own encryption when handed the key. It finds nothing. It acts only on the spans it is given, so text a caller does not list reaches the answer unchanged; finding the spans is the work of core/security/presidio-analyzer, and a caller that masks text calls both. Reachability is a deliberate part of the model. The service authenticates no caller: whatever can reach its address can submit text to it, and every text it is sent reaches it unmasked. It is published on an in-cluster address for the component that calls it, and is not meant to be exposed beyond the cluster. core/gateway/litellm takes it on its pii_anonymizer socket. Realized on Kubernetes by its Helm Recipe and for local development by its Compose Recipe, each running the vendor's published image as a single stateless service. Exports its host, port, endpoint and protocol to consumers via the uses topology, where the endpoint is the base URL a caller posts to.
Procedencia
- Digest del contenido
- sha256:f90acaf8720bddaf73930732a99f1ac28e5b24f31ecffd21c4ac80b9f6029d09
- Publicado
- 2026-11-10T10:13:54Z
- Identidad de firma
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Firma
- Oficialapplication/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:7231a93158d297fe63f76860087e3a650cbf5c780dcc7751fcea14040c16ee99
Referencia en esta versión
oci://hub.aggrega.ai/component/core/security/presidio-anonymizer:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
No se declararon parámetros del desarrollador.
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 3000 | no | Port the service listens on and its Service accepts callers on. Most operators should omit this and let the Recipe assign the default (3000), the port the published image listens on unless told otherwise. |
| engine_version | string | 2.2.364 | no | Image tag of the anonymizer the Recipe runs, from the vendor's own container registry. |
| compute | object | — | no | — |
Contrato de salida
Valores que este componente publica para los consumidores a través de la topología uses.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| host | string | — | sí | In-cluster DNS name of the Service fronting the anonymizer. Every caller reaching this name can submit text, so it is an address for the component that calls the service rather than one to publish. |
| port | integer | — | sí | TCP port that Service accepts callers on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default. |
| endpoint | string | — | sí | Base URL of the anonymizer's HTTP API, with the host and the port already composed and no path. A caller posts the text and the spans to replace to the anonymize route under it. |
| protocol | string | — | no | URL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`. |
Sockets uses
Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.
No se declararon sockets uses.
Slots de acoplamiento
Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.
No se declararon slots de acoplamiento.
Lista de permitidos de autoinyección
No se declararon canales de autoinyección.
Relaciones
Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.
Usa
Esta entidad no usa nada del catálogo.
Usado por
usa el socket «auth_core»
usa el socket «auth_core»
usa el socket «auth_core»
usa el socket «auth_core»
usa el socket «pii_anonymizer»
usa el socket «upstream»
usa el socket «forward_target»
usa el socket «scrape_target»
usa el socket «store»
usa el socket «jailbreak_detection»
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
implementa
implementa