Run your dbt Core or dbt Fusion projects as Apache Airflow DAGs and Task Groups with a few lines of code
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 81%
Response Time: 3d
First Timer Success: 58%
astronomer/astronomer-cosmos has a recorded first-timer success rate of 58.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in astronomer/astronomer-cosmos respond to incoming external pull requests in approximately 69.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 57.5 places astronomer/astronomer-cosmos in the A tier.
The external contributor pull request merge rate for astronomer/astronomer-cosmos is 81.3%, based on public PR activity from non-core contributors.
astronomer/astronomer-cosmos currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (63% critical review signals). Ensure PRs strictly follow guidelines before requesting review in astronomer/astronomer-cosmos.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/astronomer/astronomer-cosmos?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~45 hours (96% approval). Large PRs (>500 lines) take ~333 hours (37% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Python.
The tool for managing conda-forge feedstocks.
Free open-source desktop app that scrapes JAV metadata and generates NFO + cover art for Jellyfin, Emby & Kodi. No Docker, no CLI — one-click install on Windows & macOS. 8 built-in sources + optional Metatube federation (30+ providers), actress collections, cross-language tag aliases, and a REST API for AI agents.
Adjacency-list trees for Django using recursive common table expressions. Supports PostgreSQL, sqlite, MySQL and MariaDB.
When a profile mapping's required secret is absent from the Airflow connection, Cosmos fails with: cosmos.exceptions.CosmosValueError: Could not find a value for secret field password. The message names neither the profile mapping, the connection, nor where Cosmos looked (cosmos/profiles/base.py:238), so users read it as a stale manifest or a cached profile rather than a connection/mapping mismatch. A common trigger: a Snowflake connection is switched from user/password to key-pair auth, while ProfileConfig still uses SnowflakeUserPasswordProfileMapping — which requires password (cosmos/profiles/snowflake/user_pass.py:24-34) and resolves it from profile_args["password"], then conn.password (base.py:288-317). Both are empty after the switch, and the resulting traceback points at env_vars rather than at the connection. Suggested message SnowflakeUserPasswordProfileMapping could not resolve the required dbt profile field 'password'. Cosmos looked in ProfileConfig(profile_args={'passwor
Description Cosmos converts an Airflow connection into a dbt profiles.yml via the configured profile mapping. The contents of the rendered profile are only logged at INFO when profile caching is disabled — when caching is enabled (the default, since enable_cache_profile = True), only the cache path is logged, not the contents. This is a meaningful diagnostic gap: a substantial class of "Cosmos generates the wrong profile" or "Cosmos drops a connection field" issues can only be confirmed by inspecting the rendered file, which requires either: Toggling AIRFLOW__COSMOS__ENABLE_CACHE_PROFILE=False and re-running, or Shelling into the worker and cat-ing the file under /tmp/cosmos/profile/<hash>/profiles.yml. Both are workable but slow, and on managed/serverless deployments (1) requires a redeploy and (2) is often impossible. Where this happens RenderConfig.ensure_profile (around lines 373-411 at the time of writing): Non-cached branch logs the full contents via logger.info("... with th
Description No response Use case/motivation No response Related issues No response Are you willing to submit a PR? Yes, I am willing to submit a PR!
Follow up on: #2230 (comment)
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to astronomer/astronomer-cosmos, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of astronomer/astronomer-cosmos acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.3% were successfully merged into the primary branch.
astronomer/astronomer-cosmos has a recorded first-timer success rate of 58.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 57.5 places astronomer/astronomer-cosmos in the Welcoming tier.
The external pull request merge rate is 81.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, astronomer/astronomer-cosmos currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for astronomer/astronomer-cosmos are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.