Laravel To Swagger Laravel Package

Product Decisions This Supports

• API documentation as a roadmap deliverable: Informs whether "publish OpenAPI 3 specs" is a feature we ship ourselves, buy as SaaS (ReadMe, Stoplight), or generate from code — this package sits in the "generate from code" bucket.
• Build vs. buy vs. adopt: Gives a low-cost, low-lock-in option for generating Swagger/OpenAPI 3 output directly from Laravel route/controller definitions, useful when evaluating whether to invest in a docs platform before committing budget.
• Developer-experience and partner-integration use cases: Supports decisions around exposing internal APIs to partners or building a developer portal, where a machine-readable spec is the prerequisite for SDK generation, Postman collections, and contract testing.
• Scope/prioritization signal: The package’s archived status and 22 stars are themselves a data point — it tells us the "code-first OpenAPI for Laravel" niche is served by larger, actively maintained alternatives, so we should not build roadmap around this specific tool.
• Prototype and internal-tooling bets: Appropriate as a spike-level dependency for internal APIs or proofs of concept where speed matters more than longevity, not for anything tied to revenue or SLAs.

When to Consider This Package

Consider it when:

• You have a small-to-medium Laravel API and want OpenAPI 3 output with minimal annotation ceremony.
• The work is internal, disposable, or time-boxed (spike, demo, hackathon, migration aid) and a stale dependency is an acceptable risk.
• You are evaluating the category and want a reference implementation to compare against L5-Swagger, Scribe, or Scramble before committing.
• Your Laravel/PHP versions are old enough that a 2022-era package still installs cleanly.

Look elsewhere when:

• Maintenance matters. This repo is archived with no release since 2022-02-15. No security patches, no Laravel 10/11+ compatibility guarantees, no issue triage — a hard blocker for anything customer-facing or long-lived.
• You need community support or hiring signal. 22 stars means thin documentation, few Stack Overflow answers, and limited pool of engineers who’ve used it.
• You require PHP 8.2+/Laravel 11+, attribute-based routing, or CI-integrated schema linting/validation — mature alternatives cover these with active release cadences.
• You need contract testing, SDK generation, or a hosted portal — that’s a platform decision (ReadMe, Stoplight, Bump.sh), not a package decision.
• You are vendor-risk-averse: archived OSS is effectively "abandonware with an MIT license," meaning you own the fork if you adopt.

How to Pitch It (Stakeholders)

To executives: This is a free, MIT-licensed Laravel package that auto-generates OpenAPI 3 specs from our API code — the kind of artifact that unblocks partner integrations, SDKs, and a developer portal. However, it is archived and unmaintained since early 2022, with a very small user base. Recommendation: do not adopt it as a platform dependency. Treat it as a signal that the category is commoditized and cheap to solve, and budget instead for an actively maintained generator (e.g., Scramble or L5-Swagger) or a hosted docs platform if external developers are on the roadmap. Cost of adoption looks like zero; cost of ownership — security patching, Laravel upgrades, forking — is non-trivial and lands on engineering.

To engineering: The package does one thing well: convert Laravel API definitions into Swagger/OpenAPI 3 config with low annotation overhead. But it’s archived with a February 2022 last release, so expect friction on modern Laravel/PHP, no security backports, and no upstream fixes. If we adopt, we adopt the fork. Better path for anything production-bound: benchmark it against Scramble (active, attribute-driven) and L5-Swagger (mature, annotation-driven), and pick based on whether we want code-first inference or explicit annotations. Use this repo only as a reference implementation or throwaway spike — not as a dependency in a service we intend to keep.