Laravel Cashier provides an expressive, fluent interface to Stripe's subscription billing services.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
laravel/cashier-stripe 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 laravel/cashier-stripe respond to incoming external pull requests in approximately 0.0 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 8.0 places laravel/cashier-stripe in the D tier.
The external contributor pull request merge rate for laravel/cashier-stripe is 0.0%, based on public PR activity from non-core contributors.
laravel/cashier-stripe currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in laravel/cashier-stripe 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/laravel/cashier-stripe?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13: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 ~16 hours (81% approval). Large PRs (>500 lines) take ~115 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 PHP.
WordPress, Git-ified. This repository is just a mirror of the WordPress subversion repository. Please do not send pull requests. Submit pull requests to https://github.com/WordPress/wordpress-develop and patches to https://core.trac.wordpress.org/ instead.
:bathtub: Clean Code concepts adapted for PHP
Effective June 1, 2021: Phabricator is no longer actively maintained.
Cashier Stripe Version 16.5.3 Laravel Version 13.9.0 PHP Version 8.3.31 Database Driver & Version mysql Ver 8.0.45-0ubuntu0.22.04.1 for Linux on x86_64 ((Ubuntu)) Description What is happening Calling currentPeriodStart or currentPeriodEnd on multiple subscriptions i.e. inside a loop causes lazy load error. Illuminate\Database\LazyLoadingViolationException Attempted to lazy load [subscription] on model [Laravel\Cashier\SubscriptionItem] but lazy loading is disabled. NoteDifferent issue than #1172 . May be related to #1477 Cause SubscriptionItem::asStripeSubscriptionItem uses lazy loaded subscription and subscription.owner public function asStripeSubscriptionItem(array $expand = []) { return $this->subscription->owner->stripe()->subscriptionItems->retrieve( $this->stripe_id, ['expand' => $expand] ); } Current Workaround creating a custom Subscription model to overwrite original currentPeriodStart / currentPeriodEnd to eager load owner on sub
Cashier Stripe Version 16.2 Laravel Version 12 PHP Version 8.4 Database Driver & Version Mysql Description Hello, I am testing out Cashier with stripe. I have come across a weird either bug or very bad logical behaviour. Scenario: A platform has 2 types of membership: 1 - Membership Silver: $4.99 2 - Membership Gold: $9.99 If a user purchase the $4.99 membership and then wants to upgrade to the $9.99 membership and i as the provider of the service wants to charge the user up front with ->swapAndInvoice(). Well, if the users card is declided or something like 3D secure fails and the user does not pay the invoice, well then the user is stuck in a state where the user has no membership, and when the user cancels the upgrade, the user will get the plan for free? Why you may ask, well because the price id for that row in subscriptions/subscription_items has changed to the $9.99 membership with a state of "past_due". So basically the application does not know the user is on the $4.99 members
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 laravel/cashier-stripe, 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 laravel/cashier-stripe acknowledge new external contributions in approximately -. 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.
laravel/cashier-stripe 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 ~-. 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 8.0 places laravel/cashier-stripe 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, laravel/cashier-stripe currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for laravel/cashier-stripe 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.