© 2025-2026 PySpect
Source: ClickPy
Circular dependencies detected in the dependency tree: apache-airflow-providers-standard → apache-airflow-providers-common-compat, apache-airflow-providers-standard → apache-airflow, apache-airflow-providers-smtp → apache-airflow, apache-airflow-providers-smtp → apache-airflow-providers-common-compat, apache-airflow-providers-common-io → apache-airflow-providers-common-compat, apache-airflow-providers-common-io → apache-airflow, apache-airflow-core → apache-airflow-task-sdk, apache-airflow-core → apache-airflow-providers-common-compat, apache-airflow-providers-common-sql → apache-airflow, apache-airflow-providers-common-sql → apache-airflow-providers-common-compat. Hidden from the diagram below to keep it an acyclic graph.
| Package | Optional | Group |
|---|---|---|
| acryl-datahub-airflow-plugin | true | integration-tests |
| apache-airflow | true | aiobotocore |
| apache-airflow-providers-apache-hive | true | amazon |
| apache-airflow-providers-common-messaging |
| true |
| amazon |
| apache-airflow-providers-common-sql | true | amazon |
4 known vulnerabilitiesLatest: PYSEC-2026-3713 — The AWS Systems Manager Parameter Store and Secrets Manager backends in Apache Airflow's Amazon provider resolved a team-scoped Connection or Variable id through the team-agnostic lookup when the team-scoped lookup missed. In a deployment running multi-team mode with either backend, a caller in one team could resolve a secret belonging to another team by supplying an id that spells out that team's namespace, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using one of these backends. Users are advised to upgrade to apache-airflow-providers-amazon 9.34.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace. View all →