Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 33%
Response Time: 6h
First Timer Success: 33%
tt-a1i/archify has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tt-a1i/archify respond to incoming external pull requests in approximately 5.7 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 58.9 places tt-a1i/archify in the A tier.
The external contributor pull request merge rate for tt-a1i/archify is 32.7%, based on public PR activity from non-core contributors.
tt-a1i/archify currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
Strict review standards in tt-a1i/archify. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in tt-a1i/archify 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/tt-a1i/archify?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (41% approval). Large PRs (>500 lines) take ~27 hours (15% approval). Keep your diff compact for rapid review.
Goal Give shared diagrams a clean, useful brand-source link without copying request-specific URL data into the visible provenance or generated markup. Proposed scope Separate the URL needed to fetch and verify a remote brand asset from the public source URL recorded in the diagram. Keep digest-pinned fetching unchanged; use a normalized HTTP(S) source link suitable for sharing. For the public provenance, omit userinfo, query strings and fragments. This proposal is about display/share metadata, not changing the actual fetch URL or silently invalidating existing pins. Acceptance and compatibility Use synthetic URL values only in tests. Verify node metadata and SVG/HTML provenance consistently use the normalized public link. Preserve the fetch URL, captured asset bytes, digest validation, redirects policy and built-in brand behavior. Keep enough origin/path information for the source link to remain useful; document any cases where a canonical landing-page link would be more appropriate.
Thanks for @tt-a1i/archify-dsh — the Skill-only bundle shape is a nice fit for DSH, and the exact-version install guidance in the README is appreciated. A local config scanner flagged one thing I wanted to raise, as a compatibility/hygiene question rather than a bug report. cordis.patch.yml line 10 uses the host's !!js YAML tag: bundledSkillDir: !!js process.getBuiltinModule('node:path').join( process.getBuiltinModule('node:path').dirname( process.getBuiltinModule('node:module') .createRequire(baseUrl).resolve('@tt-a1i/archify-dsh/package.json')), 'skills') In DSH 0.1.5-rc.1 that tag is not inert: @deepseek-ai/cordis-plugin-loader parses it into { __jsExpr } and evaluates it at entry activation with new Function("ctx", "expr", "with (ctx) { return eval(expr) }") so it runs in the host process at boot, outside the agent sandbox, and it has access to process, process.env, node:fs, node:child_process and fetch (verified by importing the host's own exported evaluate). You
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 tt-a1i/archify, 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 tt-a1i/archify acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 32.7% were successfully merged into the primary branch.
tt-a1i/archify has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 58.9 places tt-a1i/archify in the Welcoming tier.
The external pull request merge rate is 32.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tt-a1i/archify 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 tt-a1i/archify 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.