Skeleton Laravel Package

Technical Evaluation

Architecture fit is poor as Laravel has established conventions (e.g., app/ for source code, routes/, resources/views/) that conflict with pds/skeleton's rigid src/, public/, and config/ requirements. Integration feasibility is low due to Laravel's framework-specific structure being incompatible with the standard's directory naming mandates. Technical risk is high: last release was in 2017, 0 dependents, and no maintenance activity for 7 years. Key questions include: Why would a Laravel project deviate from its own well-documented conventions? Does the team have justification to override Laravel's ecosystem tooling (e.g., Artisan, Composer autoloading) that relies on default directory structures?

Integration Approach

Stack fit is fundamentally incompatible – Laravel's app/ directory (not src/) is hard-coded into its autoloader and tooling. Migration path would require manually renaming core directories (e.g., app/ → src/), breaking all framework integrations and third-party packages. Compatibility is nonexistent: Laravel's config/ is valid per pds/skeleton, but routes/, database/, and resources/ (used differently in Laravel) would violate the standard. Sequencing is not recommended – any attempt to enforce this standard would require abandoning Laravel's native architecture, making it impractical for real-world projects.

Operational Impact

Maintenance burden would be high due to no active maintenance of the package since 2017 and no community support. Support would be nonexistent – no recent issues, PRs, or documentation updates. Scaling is irrelevant as the standard imposes structural constraints that conflict with Laravel's deployment patterns (e.g., public/ usage aligns, but Laravel's bootstrap/ and storage/ directories would be misaligned). Failure modes include broken Composer autoloading, failed Artisan commands, and incompatible third-party packages. Ramp-up would be steep as developers must unlearn Laravel conventions to adopt an obsolete standard with zero adoption in the PHP ecosystem.