The open-source agent harness - the runtime layer that turns an LLM into a working agent.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 9%
Response Time: -
First Timer Success: 10%
truefoundry/trueforge has a recorded first-timer success rate of 10.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in truefoundry/trueforge 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 65.7 places truefoundry/trueforge in the A tier.
The external contributor pull request merge rate for truefoundry/trueforge is 8.8%, based on public PR activity from non-core contributors.
truefoundry/trueforge currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The open-source agent harness - the runtime layer that turns an LLM into a working agent.
Highly welcoming maintainers in truefoundry/trueforge. Prompt code reviews with positive guidance for new contributors.
Discussions in truefoundry/trueforge focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/truefoundry/trueforge?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (11% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Summary Add Tavily as a web search provider in TrueForge so it can be configured via the settings API and used from agent turns. Why Tavily is widely used for agent web search. It fits the same singleton settings model we already use (one provider per tenant, swap via PUT). Current model Web search is one provider per tenant: Catalog lists shipped presets Settings GET / PUT create or replace the single configured provider Wire name can stay derived from type Secrets redacted on read; PUT with a redacted value keeps the stored secret Runtime resolves the configured provider when a turn needs web search Tavily should plug in as type: tavily. Requirements Ship a Tavily catalog preset Support configuring Tavily through the settings API When Tavily is configured, agent turns can run web search through Tavily When nothing is configured, web search stays disabled in capabilities Cover the usual cases in tests: upsert, optional key / redaction as applicable Auth API key should be optional:
Summary Add Exa as a web search provider in TrueForge so it can be configured via the settings API and used from agent turns. Why Exa is a common choice for agentic / semantic web search. We want it as an option next to other providers without changing the overall settings model. Current model Web search is one provider per tenant: Discover presets via the web-search catalog Configure via settings GET / PUT (upsert replaces the whole config) manifest.type selects the provider; API keys are stored server-side and redacted on read Capabilities / turns only expose web search when a provider is configured Exa should follow that same pattern (type: exa + API key). Requirements Support Exa via the settings API with an API key; rotate or keep the key on later PUTs (same redaction behavior as other secrets) When Exa is configured, agent turns can run web search through Exa When nothing is configured, web search stays disabled in capabilities Fail clearly on missing/invalid credentials Note
What happened? My Daytona configuration was older than 2 weeks in my DB, and the key I was using was expired. When I went to settings/sandbox-providers page I got a internal server error. This was because the ACCESS_DENIED in the get sandbox providers was unhandled, we should handle it. Also same can be observed while asking a agent to do something in Sandbox if your key is expired, this case is unhandled. Ideally we should handle it and mark the status of the sadbox provider as failed and give a proper status_reason. How many more places can this be unhandled? Steps to reproduce Create a key in daytona with all the necessary permissions in daytona. Configure it in platform - watch everything works Revoke the key from Daytona Create turn and ask to use sandbox, watch the unhandled error(first error) In the DB set the updated_at less than 13 days(for faster repro) Go to settings page in sandbox provider section - see the unhandled error How are you running TrueForge? Docker Compose Ve
What problem are you trying to solve? I want to run TrueForge against my own Daytona instance (the Docker Compose deployment) instead of Daytona Cloud, for local development and for keeping sandbox execution inside my own infrastructure. There's no way to tell TrueForge where that instance is — the sandbox provider manifest has no field for the API endpoint, and Settings only asks for an API key. https://github.com/daytonaio/daytona/releases/tag/v0.190.0
What problem are you trying to solve? When a user cancels a turn, the turn today waits for any running sandbox execution until that execution times out. Proposed solution Support abort on the exec tool only. Do not add abort to other sandbox operations. Give AbortSignal to Sandbox at construct time through SandboxOptions. The factory already receives the signal. Current behavior: TurnSandboxFactory input includes signal: AbortSignal. TurnResourceResolver.resolveSandbox sends signal to the factory. The turn sandbox factory in turns.ts does not use the signal. It only reads spec, existingSandboxId, and tracing. buildTurnSandbox and SandboxOptions do not take a signal. Plan: Add optional signal?: AbortSignal to SandboxOptions. Keep that signal on the Sandbox instance when present. Add optional signal?: AbortSignal to SandboxExecParams. From Sandbox, send this.signal only on the exec tool path (handleExec → provider.exec). Do not send the turn signal on init, skills, or mkdir. Do not
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 truefoundry/trueforge, 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 truefoundry/trueforge acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 8.8% were successfully merged into the primary branch.
truefoundry/trueforge has a recorded first-timer success rate of 10.0%. 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 65.7 places truefoundry/trueforge in the Welcoming tier.
The external pull request merge rate is 8.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, truefoundry/trueforge currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for truefoundry/trueforge 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.