Api Doc Bundle Laravel Package

Product Decisions This Supports

• API surface strategy (public / partner / internal). Annotation-driven doc generation answers a recurring PM question: what exactly are we exposing, and can we hand it to a partner or publish a developer portal? If docs can be produced from the code that already exists, publishing an API becomes a scoped feature rather than a documentation project.
• Build vs. buy vs. fork. This package represents the "adopt an existing docs pipeline" path. It informs the decision to spend engineering time on a generated-docs toolchain instead of hand-written Markdown/Confluence specs, which historically drift from reality within one release cycle.
• Release readiness criteria. If docs are generated from annotations, "docs updated" becomes an automatic property of a merged PR rather than a gate someone has to remember. That's a definition-of-done decision a PM can make unilaterally and cheaply.
• Support and onboarding cost. Self-serve API docs are a lever on integration time, sales-engineering effort, and support ticket volume — measurable outcomes a PM can put in a business case.
• What this package specifically does not support. With 0 stars, 0 dependents, and a last release of 2019-12-30, this fork provides no evidence base for a build-vs-buy argument. It cannot be used to benchmark alternatives, and it should not anchor a roadmap commitment. The decision it actually informs is "which maintained tool do we standardize on?" — and the answer isn't this one.

When to Consider This Package

Consider it only as a fork under ownership. This is a fork of nelmio/NelmioApiDocBundle, a well-established Symfony bundle for generating Swagger/OpenAPI documentation from annotations. The fork itself shows no adoption signal and no releases since 2019. It is viable only if you (a) have a specific patch you need to pin, (b) have a named maintainer who will own dependency bumps and security patches, and (c) have a documented route back to upstream.

Look elsewhere in most cases:

• You're on Laravel. This is a Symfony bundle, not a Laravel package — it needs service-provider bridging and brings Symfony HTTP/annotation dependencies with it. Use dedoc/scramble, knuckleswtf/scribe, darkaonline/l5-swagger, or zircote/swagger-php instead.
• You're on Symfony and just want the feature. Adopt upstream nelmio/api-doc-bundle directly. It's maintained and supports modern PHP attributes and OpenAPI.
• You need OpenAPI 3.1, request/response validation, or a hosted docs portal. The 2019 cutoff makes newer spec support unlikely.
• You need vendor or community support. 0 dependents means no community, no issue triage, no third-party fixes to inherit.
• You're on PHP 8.2+ / Symfony 6+. Expect dependency constraint conflicts; verify in a spike before committing.

Adoption checklist: maintenance cadence, license compatibility, security advisory process, CI coverage against your exact PHP/framework versions, and an explicit exit/migration plan. This package fails at least three of these on inspection.

How to Pitch It (Stakeholders)

Bottom line up front: the pattern — generating API docs from controller annotations so documentation cannot drift from code — is sound and worth adopting. This specific fork is not a recommendation. It is an unmaintained 2019 copy of a package that is actively maintained elsewhere. Recommend a short spike using the upstream bundle (Symfony) or a Laravel-native equivalent, and treat this fork as reference material only.

To executives: the value is faster partner/customer integration and lower support load; the cost is engineering ownership, not licensing. Adopting a stale fork converts a small tooling decision into a permanent maintenance liability and a supply-chain review item — a poor trade for a docs generator.

To engineering: low effort on Symfony via upstream; non-trivial on Laravel because this is a Symfony bundle requiring adaptation. The fork carries stale dependency constraints, no PHP 8 attribute support guarantees, and no security patch path. Flag it in dependency review rather than importing it transitively.

Recommended next step: one-day spike comparing upstream nelmio/api-doc-bundle against your framework-native options, with a single success criterion — docs generated from existing controllers with no manual step — and a hard rule that any docs tool we adopt must have a release in the last 12 months and at least one named owner internally.