← Back to the AI Dependency AtlasExact package identity dossier

OpenCV

pypi:opencv-python
pypi

This dossier links the stable identity pypi:opencv-python to 4 exact observed versions across 4 public repositories.

pypipypi:opencv-pythonecosystem: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
4repositories
6exact evidence rows
4exact versions
1reported license expression
0OSV 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.10.0.8417 Jun 2024
Repositories
1
Occurrences
1
Reported licenses
Apache-2.0
no verified publish attestation reportedNo OSV record returned for this exact version
Open exact source ↗
Exact version4.11.0.8616 Jan 2025
Repositories
2
Occurrences
3
Reported licenses
Apache-2.0
no verified publish attestation reportedNo OSV record returned for this exact version
Open exact source ↗
Exact version4.12.0.8807 Jul 2025
Repositories
1
Occurrences
1
Reported licenses
Apache-2.0
no verified publish attestation reportedNo OSV record returned for this exact version
Open exact source ↗
Exact version4.13.0.9205 Feb 2026
Repositories
1
Occurrences
1
Reported licenses
Apache-2.0
no verified publish attestation reportedNo OSV record returned for this exact version
Open exact source ↗
Observed relations

Repositories carrying this identity

SmartPlanAI Anwendungsh/digitalhub-sh/landesprogramm-offene-innovationen/ki-bauleitplaene/smartplanai-anwendung
4.12.0.88 · 4.13.0.922 Occurrences
Ressource Efficient Computer Visionuba-ki-lab/ressource-efficient-computer-vision
4.11.0.862 Occurrences
Objection managementuba-ki-lab/objection-management
4.10.0.841 Occurrence
photovoltaic_systemsuba-ki-lab/photovoltaic_systems
4.11.0.861 Occurrence
Exact published evidence

exact evidence rows

Objection managementuba-ki-lab/objection-management
pypi:opencv-python@4.10.0.84uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
photovoltaic_systemsuba-ki-lab/photovoltaic_systems
pypi:opencv-python@4.11.0.86sbom.json
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
Ressource Efficient Computer Visionuba-ki-lab/ressource-efficient-computer-vision
pypi:opencv-python@4.11.0.86pyproject.toml
direct declarationnot marked as development-only
Open exact source ↗
Ressource Efficient Computer Visionuba-ki-lab/ressource-efficient-computer-vision
pypi:opencv-python@4.11.0.86uv.lock
declaration relationship not reporteddevelopment scope not reported
Open exact source ↗
SmartPlanAI Anwendungsh/digitalhub-sh/landesprogramm-offene-innovationen/ki-bauleitplaene/smartplanai-anwendung
pypi:opencv-python@4.12.0.88blp_streamlit_pipeline/src/ext/streamlit-draw-image-mask/poetry.lock
declaration relationship not reportednot marked as development-only
Open exact source ↗
SmartPlanAI Anwendungsh/digitalhub-sh/landesprogramm-offene-innovationen/ki-bauleitplaene/smartplanai-anwendung
pypi:opencv-python@4.13.0.92poetry.lock
declaration relationship not reportednot marked as development-only
Open exact source ↗
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): OpenCV — exact AI dependency evidence dossier, data state 19 Jul 2026. https://i6eal.de/en/tools/ki-abhaengigkeitsatlas/paket/opencv-python-bfa06e24/

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