hookdeck/outpost - Open Source PR Review Scorecard

Open Source Outbound Webhooks and Event Destinations Infrastructure

C-Rank Grade: S (Elite) - 75/100

External PR Merge Rate: 92%

Response Time: <1h

First Timer Success: 100%

Frequently Asked Questions

Is hookdeck/outpost welcoming to first-time open-source contributors?

hookdeck/outpost has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in hookdeck/outpost respond to incoming external pull requests in approximately 0.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 75.4 C-Rankâ„¢ score (S Tier) represent?

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 75.4 places hookdeck/outpost in the S tier.

What is the external contributor pull request merge rate for hookdeck/outpost?

The external contributor pull request merge rate for hookdeck/outpost is 91.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in hookdeck/outpost?

hookdeck/outpost currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

hookdeck
hookdeck/outpostS•Elite1.0k
GitHub
Back to Explorer
hookdeck

hookdeck/outpost

1,048
S•Elite(75/100)Go

Open Source Outbound Webhooks and Event Destinations Infrastructure

Compare•
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in hookdeck/outpost welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
<1 hour
âš¡ Fast reviewer response

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
91.7%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
91.7%
Merge Gauge
100.0%
1st-Timer
Community Vibe97/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for hookdeck/outpost
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/hookdeck/outpost)](https://getmerged.abhishekco.de/hookdeck/outpost?utm_source=github&utm_medium=badge)

Active Good First Issues (2)

View on GitHub

Is your feature request related to a problem? Please describe. We run our integration platform on Cloudflare Workers with CF Queues for async processing. Outpost's filtering and subscription management capabilities would be perfect for our event fan-out needs, but we can't deliver events directly to our existing CF Queues infrastructure. Currently, to get events from Outpost into CF Queues, we'd need to: Set up a webhook destination pointing to a CF Worker Have that Worker validate and forward to the Queue This adds an extra network hop, additional Worker invocations (cost), and another failure point in the delivery chain. Describe the solution you'd like Add a cloudflare_queues destination type that publishes directly to Cloudflare Queues via the Queues HTTP API. Configuration fields: account_id (required) - Cloudflare Account ID queue_id (required) - Queue ID to publish to Credential fields: api_token (required, sensitive) - Cloudflare API Token with queues:write permission API

📅 Opened Jan 22, 2026💬 5 comments
Quality: 70/100Contribute

Is your feature request related to a problem? Please describe. It would be really nice if updating a destination also enabled it if it was previously disabled. This can either be opt-in behavior via a query param, or automatic behavior. Describe the solution you'd like If it was a query param, then something like enable=true could work. Describe alternatives you've considered The current solution is to call the enable destination right after the update destination request, which is a viable workaround. Additional context N/A

📅 Opened Jan 7, 2026💬 1 comment
Quality: 30/100Contribute
Looking for more Go beginner tasks?Explore Go GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for hookdeck/outpost

When evaluating whether to contribute to hookdeck/outpost, 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 hookdeck/outpost acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 91.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to hookdeck/outpost

01

Is hookdeck/outpost welcoming to first-time open-source contributors?

hookdeck/outpost has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 75.4 C-Rankâ„¢ score represent?

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 75.4 places hookdeck/outpost in the Elite tier.

04

What is the external contributor pull request merge rate for hookdeck/outpost?

The external pull request merge rate is 91.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in hookdeck/outpost?

Yes, hookdeck/outpost currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rankâ„¢ Indexing Standard

All metrics displayed for hookdeck/outpost 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.

hookdeck/outpost • 75.4/100 C-Rank (S-Tier) | GetMerged