Models Laravel Package

Product Decisions This Supports

• Not recommended for Laravel projects—this package remains tightly coupled to the Spiral Framework and lacks Laravel compatibility. The recent refactoring (moving schema commands out of the entity) suggests internal architectural changes but does not address Laravel integration.
• Legacy Spiral projects may still use this for schema validation/mutators, but no new adoption is justified due to:
  • No Laravel support (no Eloquent, service provider, or Laravel-specific features).
  • Outdated maintenance (last major release in 2019; v2.2.1 is a minor tweak, not a revival).
  • Better alternatives exist (e.g., Spatie Data, Laravel DTOs, or native Eloquent mutators).
• Roadmap consideration: If evaluating Spiral Framework migration tools, this package’s schema handling might inform decisions—but it’s not a standalone solution.

When to Consider This Package

• Only for existing Spiral Framework projects where:
  • The package is already integrated and migration costs outweigh risks.
  • The team is committed to Spiral and lacks budget/resources for a rewrite.
• Avoid if:
  • Building a new Laravel project (use Eloquent, Spatie Data, or Laravel DTOs instead).
  • Seeking active maintenance (3 GitHub stars, no recent commits beyond minor fixes).
  • Prioritizing security (unpatched dependencies in an abandoned ecosystem).
  • The refactoring in v2.2.1 introduces breaking changes for dependent Spiral projects (schema command relocation may require updates to custom logic).

How to Pitch It (Stakeholders)

Executives: "This package is a Spiral Framework tool—not Laravel-compatible—and hasn’t seen meaningful updates in years. The recent v2.2.1 release is a minor internal refactor, not a product revival. We’d face technical debt, security risks, and integration challenges. For Laravel, we should invest in actively maintained alternatives like Spatie Data, which align with our stack and roadmap."

Engineering: *"The schema command refactor in v2.2.1 is irrelevant to Laravel. If we’re maintaining a legacy Spiral app, we can assess the impact—but for new work, this package is a dead end. Recommend evaluating:

1. Laravel-native solutions (Eloquent, Spatie Data) for schema validation.
2. Spiral migration tools (if applicable) to phase out this dependency.
3. Security audits if this package is currently in production (risk of unpatched vulnerabilities)."*