Routing Laravel Package

Product Decisions This Supports

• Default decision: do not add this package to a Laravel product. Laravel already provides routing, middleware integration, route model binding, URL generation, and related conventions. marko/routing is a read-only split of the Marko Framework’s routing component, not a Laravel routing integration.
• Build vs. buy: No buy decision is warranted for Laravel work. If the team is evaluating Marko as a framework, routing should be assessed as part of the whole framework decision, not adopted as a standalone dependency.
• Roadmap impact: None for Laravel-based products. This package does not justify a roadmap item, migration, or architecture change unless the organization is explicitly standardizing on Marko.
• Use cases supported: Only Marko-based applications that need the framework’s native routing layer. It is not positioned as a general-purpose router for Laravel, Symfony, or standalone PHP applications.
• Risk signal: Zero stars, zero dependents, and a read-only repository indicate very low public adoption and a governance model tied to the parent Marko monorepo. Treat it as framework-internal infrastructure, not a commercially supported component.

When to Consider This Package

• Consider only if your team has already selected the Marko framework and needs its native routing component as part of that stack.
• Consider for evaluation only if you are benchmarking PHP framework routing approaches and want to inspect Marko’s implementation under its MIT license.
• Do not consider it for Laravel applications, where native routing is the lower-risk, lower-cost, better-supported choice.
• Look elsewhere for standalone routing needs: use Laravel’s router, Symfony Routing, FastRoute, or another mature router with active adoption, documentation, and support.
• Look elsewhere immediately if you need vendor support, SLAs, broad community answers, or a package with independent issue tracking. This repository is read-only, and issues/PRs are directed to the parent Marko project.

How to Pitch It (Stakeholders)

Executive summary: This is not a strategic dependency for our Laravel/PHP products. It is a framework-internal routing component for Marko, with effectively no independent adoption signals and a read-only repository. Adopting it would add ecosystem risk without solving a Laravel problem. Recommendation: do not budget for adoption; continue using Laravel’s native routing.

Engineering summary: marko/routing is MIT-licensed but not a Laravel package. It should only be relevant if we are evaluating the Marko framework as a whole. For any Laravel service, using native routing is simpler, better documented, and avoids coupling to a low-adoption framework component. If Marko is ever considered, assess the full framework’s maturity, support model, and migration cost rather than treating this split package as an independent build-vs-buy decision.