i6eal.de
DEEN
Start a project
← Back to the AI Dependency AtlasExact package identity dossier

anyio

pypi:anyio
pypi

This dossier links the stable identity pypi:anyio to 9 exact observed versions across 18 public repositories.

pypipypi:anyioecosystem:name + exact version + evidence path

A package identity or provider interface in published code does not prove configuration, an account, procurement, data transfer or an API call.

ecosystem:name + exact version + evidence path
18repositories
19exact evidence rows
9exact versions
1reported license expression
2OSV records returned
Exact published evidence

Observed exact versions and registry metadata

Publication age and licenses come from deps.dev metadata. They are context—not a maintenance, legal or portability verdict.

Exact version4.3.019 Feb 2024
Repositories
1
Occurrences
1
Reported licenses
MIT
no verified publish attestation reported2 OSV records
Open exact source ↗
Exact version4.5.214 Oct 2024
Repositories
1
Occurrences
1
Reported licenses
MIT
no verified publish attestation reported2 OSV records
Open exact source ↗
Exact version4.8.005 Jan 2025
Repositories
1
Occurrences
1
Reported licenses
MIT
verified publish attestation2 OSV records
Open exact source ↗
Exact version4.9.017 Mar 2025
Repositories
3
Occurrences
3
Reported licenses
MIT
verified publish attestation2 OSV records
Open exact source ↗
Exact version4.10.004 Aug 2025
Repositories
1
Occurrences
1
Reported licenses
MIT
verified publish attestation2 OSV records
Open exact source ↗
Exact version4.11.023 Sept 2025
Repositories
5
Occurrences
5
Reported licenses
MIT
verified publish attestation2 OSV records
Open exact source ↗
Exact version4.12.106 Jan 2026
Repositories
2
Occurrences
2
Reported licenses
MIT
verified publish attestation2 OSV records
Open exact source ↗
Exact version4.13.024 Mar 2026
Repositories
3
Occurrences
4
Reported licenses
MIT
verified publish attestation2 OSV records
Open exact source ↗
Exact version4.14.212 Jul 2026
Repositories
1
Occurrences
1
Reported licenses
MIT
verified publish attestationNo OSV record returned for this exact version
Open exact source ↗
Observed relations

Repositories carrying this identity

MUCGPTlandeshauptstadt-muenchen/mucgpt
4.13.02 Occurrences
→
kiva-llm-gatewaybaden-wuerttemberg/innenministerium/kiva.platform/kiva-llm-gateway
4.5.21 Occurrence
→
ai-websearch-benchmarkdatenlabor-bmz/ai-websearch-benchmark
4.12.11 Occurrence
→
AIiqsh/collaboration-online-board/ai
4.3.01 Occurrence
→
SmartPlanAI Anwendungsh/digitalhub-sh/landesprogramm-offene-innovationen/ki-bauleitplaene/smartplanai-anwendung
4.13.01 Occurrence
→
LLM Servicesh/diwish/splitbot/kosmo/llm-service
4.14.21 Occurrence
→
Coding Agent Usage Simulationuba-ki-lab/coding-agent-usage-simulation
4.11.01 Occurrence
→
GSA Extractionuba-ki-lab/gsa-extraction
4.9.01 Occurrence
→
LLM Questionnaire Benchmarking Frameworkuba-ki-lab/llm-questionnaire-benchmarking-framework
4.10.01 Occurrence
→
LLM Testframeworkuba-ki-lab/llm-testframework
4.9.01 Occurrence
→
Objection managementuba-ki-lab/objection-management
4.8.01 Occurrence
→
Ressource Efficient Computer Visionuba-ki-lab/ressource-efficient-computer-vision
4.12.11 Occurrence
→
Retrieval Evaluationuba-ki-lab/retrieval-evaluation
4.11.01 Occurrence
→
strahlenexpositionuba-ki-lab/strahlenexposition
4.9.01 Occurrence
→
Workshop Green LLM Usageuba-ki-lab/workshop-green-llm-usage
4.11.01 Occurrence
→
URBAN.KI AirGuardAIvernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-airguardai
4.13.01 Occurrence
→
URBAN.KI SmartEnergievernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-smartenergie
4.11.01 Occurrence
→
URBAN.KI Sovia-appvernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-sovia-app
4.11.01 Occurrence
→
Exact published evidence

exact evidence rows

AIiqsh/collaboration-online-board/ai
pypi:anyio@4.3.0SPDX_v2.0.0.yml
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
ai-websearch-benchmarkdatenlabor-bmz/ai-websearch-benchmark
pypi:anyio@4.12.1uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Coding Agent Usage Simulationuba-ki-lab/coding-agent-usage-simulation
pypi:anyio@4.11.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
GSA Extractionuba-ki-lab/gsa-extraction
pypi:anyio@4.9.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
kiva-llm-gatewaybaden-wuerttemberg/innenministerium/kiva.platform/kiva-llm-gateway
pypi:anyio@4.5.2poetry.lock
declaration relationship not reportednot marked as development-only
Open exact source ↗
LLM Questionnaire Benchmarking Frameworkuba-ki-lab/llm-questionnaire-benchmarking-framework
pypi:anyio@4.10.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
LLM Servicesh/diwish/splitbot/kosmo/llm-service
pypi:anyio@4.14.2uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
LLM Testframeworkuba-ki-lab/llm-testframework
pypi:anyio@4.9.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
MUCGPTlandeshauptstadt-muenchen/mucgpt
pypi:anyio@4.13.0mucgpt-assistant-service/uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
MUCGPTlandeshauptstadt-muenchen/mucgpt
pypi:anyio@4.13.0mucgpt-core-service/uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Objection managementuba-ki-lab/objection-management
pypi:anyio@4.8.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Ressource Efficient Computer Visionuba-ki-lab/ressource-efficient-computer-vision
pypi:anyio@4.12.1uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Retrieval Evaluationuba-ki-lab/retrieval-evaluation
pypi:anyio@4.11.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
SmartPlanAI Anwendungsh/digitalhub-sh/landesprogramm-offene-innovationen/ki-bauleitplaene/smartplanai-anwendung
pypi:anyio@4.13.0poetry.lock
declaration relationship not reportednot marked as development-only
Open exact source ↗
strahlenexpositionuba-ki-lab/strahlenexposition
pypi:anyio@4.9.0sbom.json
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
URBAN.KI AirGuardAIvernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-airguardai
pypi:anyio@4.13.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
URBAN.KI SmartEnergievernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-smartenergie
pypi:anyio@4.11.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
URBAN.KI Sovia-appvernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-sovia-app
pypi:anyio@4.11.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Workshop Green LLM Usageuba-ki-lab/workshop-green-llm-usage
pypi:anyio@4.11.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
OSV

Related OSV records

GHSA-5p39-cfhj-2xmp

AnyIO process-pool workers can block indefinitely on undrained stderr

17 repositories18 Sept 2026
→
GHSA-82r6-8w77-94w6

AnyIO: TLSStream IDNA 2003 host name encoding enables potential TLS certificate spoofing

17 repositories18 Sept 2026
→
Interpretation boundary

Exact identities in, explicit limits out

Only exact npm and PyPI tuples are enriched. Reported SPDX expressions are metadata; no compatibility, obligation or legal conclusion is inferred.

Retrieval, parsing, matching and publishing use no generative AI model.

i6eal (2026): anyio — exact AI dependency evidence dossier, data state 19 Sept 2026. https://i6eal.de/en/tools/ki-abhaengigkeitsatlas/paket/anyio-399e5280/

Reading this dossier

Does package presence prove that a provider is used?
No. Even a direct interface declaration does not establish configuration, credentials, procurement, data transfer or an API call.
Why are exact versions required?
OSV and registry metadata can be linked reproducibly only to an observed package@version tuple. The collector never substitutes a newest release for a range.
Does a missing row mean the dependency is absent?
No. It means not observed within the bounded files and repository checkpoint. Incomplete trees and parser failures remain explicit.

Need a permanent dependency evidence trail for another public code cohort?

We build source-backed data products with stable identities, reproducible joins and boundaries that remain visible.

Discuss a data projectExplore all tools
Related tools

Useful next steps

These tools complement the current result.

View all tools
MonitorGerman public-sector AI Code RadarWhich AI building blocks does German public administration publish as open code? Exact packages, containers, commit SHAs and file paths from openCode, with permanent dossiers and no deployment claim.MonitorGerman public-sector AI registerWhere does German public administration already use AI? Search published system profiles from federal, state and municipal bodies, with lifecycle, governance fields, stable identifiers and original evidence.Provenance checkPublic-sector AI system passportSee which public records can be linked to each published government AI system through stable identifiers or exact source-declared repository URLs—with a source for every edge and visible evidence boundaries.