Local security audit for AI API relays and LLM proxies: detects prompt injection, model substitution, tool-call rewriting, SSE anomalies, error leakage, and Web3 wallet risks.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 60%
Response Time: 18h
First Timer Success: 100%
toby-bridges/api-relay-audit has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in toby-bridges/api-relay-audit respond to incoming external pull requests in approximately 17.9 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 56.2 places toby-bridges/api-relay-audit in the A tier.
The external contributor pull request merge rate for toby-bridges/api-relay-audit is 60.0%, based on public PR activity from non-core contributors.
toby-bridges/api-relay-audit currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in toby-bridges/api-relay-audit welcoming community pull requests and bug fixes.
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/toby-bridges/api-relay-audit?utm_source=github&utm_medium=badge)
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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (75% approval). Large PRs (>500 lines) take ~86 hours (27% approval). Keep your diff compact for rapid review.
Add short command examples showing when to use --profile general, --profile web3, and --profile full. Keep the examples local-first and avoid suggesting that any profile certifies a relay as safe.
Expand the Web3 profile documentation around transfer guidance, signed-transaction refusal, private-key refusal, and signature-isolation risks. The goal is clearer user guidance before wallet-related relay traffic is trusted.
Current tool-call rewriting detection focuses on text-echo package command integrity. Track future work for structured tool payloads, coding-agent tool calls, and package-install mutation cases without overclaiming current coverage.
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 toby-bridges/api-relay-audit, 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 toby-bridges/api-relay-audit acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.0% were successfully merged into the primary branch.
toby-bridges/api-relay-audit has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 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 56.2 places toby-bridges/api-relay-audit in the Welcoming tier.
The external pull request merge rate is 60.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, toby-bridges/api-relay-audit currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for toby-bridges/api-relay-audit 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.