Component
core/security/presidio-analyzer
The Presidio analyzer: a service that finds personal and other sensitive data in text. A caller posts a text, the language it is written in and, optionally, the entity types it is looking for — person names, email addresses, phone numbers, card and bank account numbers, national identifiers and the like — and the service answers with where each match sits in the text, which type it is and how confident the match is. It changes nothing: replacing what it found is the work of core/security/presidio-anonymizer, so a caller that masks text calls both. core/gateway/litellm takes it on its pii_analyzer socket. Recognition is in English only, the one language the published image loads a model for. It is automated recognition, so it misses some sensitive data and marks some text that is not sensitive; other protections belong beside it. It authenticates no caller, and every text reaches it unmasked, so it is published on an in-cluster address for the component that calls it and is not meant to be exposed beyond the cluster. 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, where the endpoint is the base URL a caller posts to.
Provenance
- Content digest
- sha256:820b79ed19d325eea180e6bb72bb14c4dc58e7750a7f9c21a8f6fc7098e1fa11
- Published
- 2026-11-10T10:13:50Z
- 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:d397ff1a10b5476617cecf7b3f252c12ef18b38675e33e40aee66904f1347847
Reference at this version
oci://hub.aggrega.ai/component/core/security/presidio-analyzer:1.0.0Developer parameters
Values the developer sets in the Aggregate.
No developer parameters declared.
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| 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 analyzer the Recipe runs, from the vendor's own container registry. |
| compute | object | — | no | — |
Output contract
Values this component publishes to consumers over the uses topology.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| host | string | — | yes | In-cluster DNS name of the Service fronting the analyzer. 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 | — | yes | 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 | — | yes | Base URL of the analyzer's HTTP API, with the host and the port already composed and no path. A caller posts the text to analyze to the analyze 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`. |
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
No uses sockets declared.
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
No attachment slots declared.
Self-inject allowlist
No self-inject pipes declared.
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
uses socket «auth_core»
uses socket «auth_core»
uses socket «auth_core»
uses socket «auth_core»
uses socket «pii_analyzer»
uses socket «upstream»
uses socket «pii_analyzer»
uses socket «forward_target»
uses socket «scrape_target»
uses socket «store»
uses socket «jailbreak_detection»
applies to
applies to
applies to
applies to
applies to
applies to
applies to
implements
implements