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

fsspec

pypi:fsspec
pypi

This dossier links the stable identity pypi:fsspec to 10 exact observed versions across 16 public repositories.

pypipypi:fsspececosystem: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
16repositories
16exact evidence rows
10exact versions
2reported license expressions
1OSV record 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 version2024.9.004 Sept 2024
Repositories
1
Occurrences
1
Reported licenses
non-standard
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2025.3.007 Mar 2025
Repositories
3
Occurrences
3
Reported licenses
non-standard
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2025.3.231 Mar 2025
Repositories
1
Occurrences
1
Reported licenses
non-standard
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2025.5.020 May 2025
Repositories
1
Occurrences
1
Reported licenses
non-standard
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2025.9.002 Sept 2025
Repositories
3
Occurrences
3
Reported licenses
BSD-3-Clause
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2025.10.030 Oct 2025
Repositories
2
Occurrences
2
Reported licenses
BSD-3-Clause
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2026.1.009 Jan 2026
Repositories
1
Occurrences
1
Reported licenses
BSD-3-Clause
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2026.2.005 Feb 2026
Repositories
2
Occurrences
2
Reported licenses
BSD-3-Clause
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2026.3.027 Mar 2026
Repositories
1
Occurrences
1
Reported licenses
BSD-3-Clause
no verified publish attestation reported1 OSV record
Open exact source ↗
Exact version2026.6.016 Jun 2026
Repositories
1
Occurrences
1
Reported licenses
BSD-3-Clause
no verified publish attestation reportedNo OSV record returned for this exact version
Open exact source ↗
Observed relations

Repositories carrying this identity

kiva-llm-gatewaybaden-wuerttemberg/innenministerium/kiva.platform/kiva-llm-gateway
2025.3.01 Occurrence
→
SmartPlanAI Anwendungsh/digitalhub-sh/landesprogramm-offene-innovationen/ki-bauleitplaene/smartplanai-anwendung
2026.3.01 Occurrence
→
LLM Servicesh/diwish/splitbot/kosmo/llm-service
2026.6.01 Occurrence
→
Coding Agent Usage Simulationuba-ki-lab/coding-agent-usage-simulation
2025.9.01 Occurrence
→
density-mapsuba-ki-lab/density-maps
2026.2.01 Occurrence
→
GSA Extractionuba-ki-lab/gsa-extraction
2025.3.01 Occurrence
→
LLM Questionnaire Benchmarking Frameworkuba-ki-lab/llm-questionnaire-benchmarking-framework
2025.9.01 Occurrence
→
LLM Testframeworkuba-ki-lab/llm-testframework
2025.3.01 Occurrence
→
Objection managementuba-ki-lab/objection-management
2024.9.01 Occurrence
→
photovoltaic_systemsuba-ki-lab/photovoltaic_systems
2025.5.01 Occurrence
→
Ressource Efficient Computer Visionuba-ki-lab/ressource-efficient-computer-vision
2026.1.01 Occurrence
→
Retrieval Evaluationuba-ki-lab/retrieval-evaluation
2025.10.01 Occurrence
→
URBAN.KI AirGuardAIvernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-airguardai
2026.2.01 Occurrence
→
URBAN.KI SmartEnergievernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-smartenergie
2025.9.01 Occurrence
→
URBAN.KI Soviavernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-sovia
2025.3.21 Occurrence
→
URBAN.KI Sovia-appvernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-sovia-app
2025.10.01 Occurrence
→
Exact published evidence

exact evidence rows

Coding Agent Usage Simulationuba-ki-lab/coding-agent-usage-simulation
pypi:fsspec@2025.9.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
density-mapsuba-ki-lab/density-maps
pypi:fsspec@2026.2.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
GSA Extractionuba-ki-lab/gsa-extraction
pypi:fsspec@2025.3.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
kiva-llm-gatewaybaden-wuerttemberg/innenministerium/kiva.platform/kiva-llm-gateway
pypi:fsspec@2025.3.0poetry.lock
declaration relationship not reportednot marked as development-only
Open exact source ↗
LLM Questionnaire Benchmarking Frameworkuba-ki-lab/llm-questionnaire-benchmarking-framework
pypi:fsspec@2025.9.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
LLM Servicesh/diwish/splitbot/kosmo/llm-service
pypi:fsspec@2026.6.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
LLM Testframeworkuba-ki-lab/llm-testframework
pypi:fsspec@2025.3.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Objection managementuba-ki-lab/objection-management
pypi:fsspec@2024.9.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
photovoltaic_systemsuba-ki-lab/photovoltaic_systems
pypi:fsspec@2025.5.0sbom.json
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Ressource Efficient Computer Visionuba-ki-lab/ressource-efficient-computer-vision
pypi:fsspec@2026.1.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Retrieval Evaluationuba-ki-lab/retrieval-evaluation
pypi:fsspec@2025.10.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
SmartPlanAI Anwendungsh/digitalhub-sh/landesprogramm-offene-innovationen/ki-bauleitplaene/smartplanai-anwendung
pypi:fsspec@2026.3.0poetry.lock
declaration relationship not reportednot marked as development-only
Open exact source ↗
URBAN.KI AirGuardAIvernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-airguardai
pypi:fsspec@2026.2.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
URBAN.KI SmartEnergievernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-smartenergie
pypi:fsspec@2025.9.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
URBAN.KI Soviavernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-sovia
pypi:fsspec@2025.3.2uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
URBAN.KI Sovia-appvernetzte-stadt-gelsenkirchen/urban.ki/urban-ki-sovia-app
pypi:fsspec@2025.10.0uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
OSV

Related OSV records

GHSA-27vj-qcqg-25rc

fsspec: Server-Side Template Injection in ReferenceFileSystem leads to Remote Code Execution

15 repositories06 Oct 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): fsspec — exact AI dependency evidence dossier, data state 06 Oct 2026. https://i6eal.de/en/tools/ki-abhaengigkeitsatlas/paket/fsspec-b1a7c311/

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 cover related ground.

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.