One Package To Rule Them All Laravel Package

Product Decisions This Supports

• Reducing Technical Debt & Maintenance Overhead: Consolidates multiple Spatie Laravel packages into a single dependency, simplifying composer.json and reducing future dependency management complexity.
• Accelerating Onboarding: Faster developer ramp-up by bundling commonly used utilities (e.g., laravel-permission, laravel-activitylog, laravel-backup) under one package, reducing configuration friction.
• Cost Optimization: Avoids licensing/legal review for multiple individual packages by adopting a single MIT-licensed solution.
• Roadmap Alignment: Ideal for projects prioritizing developer experience (DX) or modularity (e.g., SaaS platforms, internal tools, or MVPs where time-to-market is critical).
• Build vs. Buy: Buy—avoids reinventing wheel for common Laravel utilities (e.g., permissions, logging, backups) while maintaining extensibility.

When to Consider This Package

• Avoid if:
  • Your project requires granular control over specific package versions (e.g., laravel-permission@5.x but laravel-backup@4.x). This package locks all Spatie deps to the latest compatible versions.
  • You need auditability of individual package usage (e.g., for compliance or cost tracking). Zero dependents = untested in production.
  • Your team prefers explicit dependencies for security/scanning tools (e.g., Snyk, Dependabot) to flag issues per package.
  • You’re using non-Spatie packages that conflict with bundled dependencies (e.g., custom permission systems).
• Look elsewhere if:
  • You need active maintenance (last release: 2021). Consider alternatives like spatie/laravel-package-tools for newer solutions.
  • Your stack includes non-Laravel/PHP components (this is PHP-only).

How to Pitch It (Stakeholders)

For Executives:

"This package cuts our vendor management in half by bundling 20+ Spatie Laravel utilities into one dependency—saving dev time on setup and reducing future tech debt. For example, a new feature requiring permissions, activity logs, and backups would normally need 3 separate packages; now it’s one line in composer.json. The MIT license and Spatie’s reputation ensure reliability, while the 60%+ reduction in dependency sprawl aligns with our [Tech Debt Reduction Initiative]."

For Engineering:

*"This is a composer.json refactor win:

• Pros:
  • Replace spatie/laravel-permission, spatie/laravel-activitylog, etc., with one package (check bundled packages).
  • Simplifies composer update and dependency conflicts.
  • Spatie’s packages are battle-tested; this just wraps them neatly.
• Cons:
  • No version pinning per package (use replace in composer.json if needed).
  • Zero active maintenance (last update: 2021)—but core functionality is stable.
• Action: Run composer require spatie/one-package-to-rule-them-all in a staging environment and validate no breaking changes. Pair with a composer.json audit to remove orphaned Spatie packages."*

For Developers:

"Imagine never manually requiring spatie/laravel-* again. This package: ✅ Auto-includes 20+ utilities (permissions, backups, media library, etc.). ✅ Reduces config files—no more hunting for spatie/laravel-permission:install commands. ✅ Future-proofs your project if you adopt more Spatie tools later. Downside: You’re stuck with whatever versions Spatie bundles (but they’re usually solid). Try it: composer require spatie/one-package-to-rule-them-all and check the README for included features."*