The batteries-included agent harness.
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 73%
Response Time: -
First Timer Success: 40%
langchain-ai/deepagents has a recorded first-timer success rate of 39.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in langchain-ai/deepagents respond to incoming external pull requests in approximately 0.0 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 63.8 places langchain-ai/deepagents in the A tier.
The external contributor pull request merge rate for langchain-ai/deepagents is 73.2%, based on public PR activity from non-core contributors.
langchain-ai/deepagents does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in langchain-ai/deepagents. Prompt code reviews with positive guidance for new contributors.
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/langchain-ai/deepagents?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (92% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
Privileged issue I am a Deep Agents maintainer. Issue Content Follow-up to #3538, which added --sandbox-snapshot-name to deepagents-code. deepagents-code now has a --sandbox-snapshot-name CLI flag that lets users boot a fresh sandbox from a named, pre-baked snapshot. It's currently rejected for every provider other than langsmith because langchain-daytona's DaytonaProvider.get_or_create accepts **kwargs and discards them — there is no plumbing for the Daytona SDK's snapshot/image primitive. Upstream status: the Daytona SDK does support snapshots/images at the API level (langchain-daytona just doesn't expose them). What we want: Expose a snapshot (or image — match Daytona's nomenclature) kwarg on the DaytonaSandbox.get_or_create path that resolves to the Daytona SDK's snapshot/image identifier. Mirror the LangSmith UX: if the named snapshot is missing, create it; otherwise reuse. Document precedence between an explicit kwarg, env vars, and a built-in default. Provide the equival
Privileged issue I am a Deep Agents maintainer. Issue Content e.g. set a default light/dark mode theme, responsive to system theme alternatively, assign a theme depending on the terminal used/some env var Upstream: Textualize/textual#2419 Textualize/textual#6151 Area (Required) deepagents (SDK) code Other / not sure / general
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 langchain-ai/deepagents, 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 langchain-ai/deepagents acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.2% were successfully merged into the primary branch.
langchain-ai/deepagents has a recorded first-timer success rate of 39.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 63.8 places langchain-ai/deepagents in the Welcoming tier.
The external pull request merge rate is 73.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
langchain-ai/deepagents does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for langchain-ai/deepagents 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.