© 2025-2026 PySpect
Source: ClickPy
Circular dependencies detected in the dependency tree: apache-airflow-providers-common-compat → apache-airflow, apache-airflow-providers-standard → apache-airflow, apache-airflow-providers-common-io → apache-airflow, apache-airflow-task-sdk → apache-airflow-core, apache-airflow-providers-common-sql → apache-airflow, apache-airflow-providers-smtp → apache-airflow. Hidden from the diagram below to keep it an acyclic graph.
| Package | Optional | Group |
|---|---|---|
| acryl-datahub-airflow-plugin | true | integration-tests |
| apache-airflow | true | all |
| apache-airflow-providers-amazon | true | |
| apache-airflow-providers-apache-kafka | true | |
| apache-airflow-providers-databricks | true |
5 known vulnerabilitiesLatest: PYSEC-2026-3714 — The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider never applied the team scope when resolving Connections and Variables: the caller's `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team's Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name. View all →