morcen/passage - Open Source PR Review Scorecard

Lightweight API proxy gateway for Laravel

C-Rank Grade: B (Solid) - 56/100

External PR Merge Rate: 91%

Response Time: 4d

First Timer Success: 67%

Frequently Asked Questions

Is morcen/passage welcoming to first-time open-source contributors?

morcen/passage has a recorded first-timer success rate of 66.7%. Repositories ranked B 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 morcen/passage respond to incoming external pull requests in approximately 87.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 56.1 C-Rank™ score (B 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 56.1 places morcen/passage in the B tier.

What is the external contributor pull request merge rate for morcen/passage?

The external contributor pull request merge rate for morcen/passage is 91.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in morcen/passage?

morcen/passage does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

morcen
morcen/passageBSolid60
GitHub
Back to Explorer
morcen

morcen/passage

60
BSolid(56/100)PHP

Lightweight API proxy gateway for Laravel

Compare
Jump to:
Response Velocity
3 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
91.0%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
91.0%
Merge Gauge
66.7%
1st-Timer
Community Vibe56/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Problem The docblock says logging "falls back to the default channel" when no passage channel exists. The code hardcodes Log::channel('passage') with no fallback, so an unconfigured channel routes through Laravel's emergency logger instead. Small, but the class exists for observability, and its own behavior is mis-documented. Location src/Listeners/PassageEventSubscriber.php Fix Check config('logging.channels.passage') and fall back to the default channel, matching the docblock. Sizing Priority 10 (Impact 1, Risk 1, Effort 1). Estimated 1 hour. From the tech debt audit dated 2026-07-05.

📅 Opened Jul 5, 2026💬 0 comments
Quality: 100/100Contribute
Looking for more PHP beginner tasks?Explore PHP 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 morcen/passage

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

Frequently Asked Questions - Contributing to morcen/passage

01

Is morcen/passage welcoming to first-time open-source contributors?

morcen/passage has a recorded first-timer success rate of 66.7%. Repositories ranked Solid 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 ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 56.1 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 56.1 places morcen/passage in the Solid tier.

04

What is the external contributor pull request merge rate for morcen/passage?

The external pull request merge rate is 91.0%. 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 morcen/passage?

morcen/passage does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for morcen/passage 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.