A secure* runtime for autonomous AI agents. Policy from plain-English constitutions. (*https://ironcurtain.dev)
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: 10h
First Timer Success: -
provos/ironcurtain has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in provos/ironcurtain respond to incoming external pull requests in approximately 10.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 29.9 places provos/ironcurtain in the D tier.
The external contributor pull request merge rate for provos/ironcurtain is 0.0%, based on public PR activity from non-core contributors.
provos/ironcurtain currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A secure* runtime for autonomous AI agents. Policy from plain-English constitutions. (*https://ironcurtain.dev)
Strict review standards in provos/ironcurtain. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in provos/ironcurtain 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/provos/ironcurtain?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15: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 ~7 hours (81% approval). Large PRs (>500 lines) take ~50 hours (29% 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 TypeScript.
A fast, simple & powerful blog framework, powered by Node.js.
开放式跨端跨框架解决方案，支持使用 React/Vue 等框架来开发微信/京东/百度/支付宝/字节跳动/ QQ 小程序/H5/React Native 等应用。
Material Design for React Native (Android & iOS)
Problem ironcurtain workflow resume <baseDir> constructs and runs a separate in-process WorkflowOrchestrator. Its resumed state is therefore not visible to the daemon-backed Web UI or to ironcurtain workflow status/await, even when the original workflow was launched from the daemon/UI. In the observed case, the legacy CLI resumed a checkpoint and dispatched harness_design, while the daemon continued to report the same workflow as phase: aborted. This creates a second, independently managed execution path against the same run artifacts/checkpoint. Desired behavior Provide a CLI resume command that calls the daemon's existing workflows.resume RPC (including an exact workflowId selector) and then returns an observable daemon-managed run. The UI, workflow status, workflow await, lifecycle events, gates, and artifact timeline should all reflect the resumed execution. The existing standalone/in-process resume behavior should either be explicitly separated and named as such or retired for dae
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 provos/ironcurtain, 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 provos/ironcurtain acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
provos/ironcurtain has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 hours. 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 29.9 places provos/ironcurtain in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, provos/ironcurtain currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for provos/ironcurtain 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.