Nova Sortable Laravel Package

Product Decisions This Supports

• Build vs. buy vs. native: decides whether admin-panel sorting is a package dependency, an in-house Nova customization, or simply a configuration of Nova's built-in sortable columns. For most teams the answer is "native feature, no dependency."
• Admin UX roadmap for internal tools: informs whether sortable index tables are table-stakes polish or a differentiator. For Nova-backed back offices, sorting is expected by default and rarely worth a dedicated roadmap item.
• Dependency risk / technical debt triage: a 2019 archive date with 32 stars is a maintenance liability signal. This supports a decision to freeze, replace, or remove the dependency during the next Nova upgrade cycle rather than carry it forward.
• Platform upgrade planning: if the product is moving to newer Nova majors or PHP 7.4+/8.x, this assessment feeds the sequencing of "remove legacy Nova add-ons" work.
• Prioritization input for a maintenance sprint: quantifies effort (small) against value (low), helping rank cleanup items against revenue-facing work.

When to Consider This Package

Consider it only when all of the following hold:

• You maintain a legacy Laravel Nova admin (roughly Nova 1.x/2.x era) where the index sorting behavior is not available natively and changing it now carries regression risk.
• The package is already installed and working in production; the question is "keep or remove," not "add."
• Your team accepts an unmaintained MIT dependency and has verified it against the PHP/Laravel versions actually deployed.
• The scope is genuinely narrow — column or row ordering on a resource index — with no security, tenancy, or permission sensitivity.

Look elsewhere when:

• You are starting a new Nova project or have upgraded to a recent Nova major — use Nova's native sortable columns and avoid the dependency entirely.
• You need PHP 8.x / current Laravel support, active security patching, or vendor SLAs. An archived 2019 package will not satisfy a security review.
• You need richer behavior — multi-column sort, persisted per-user sort preferences, drag-and-drop ordering with audit trails — which is better served by a small in-house implementation you own.
• The admin panel is customer-facing or revenue-critical, where an abandoned dependency is a disproportionate risk for the value delivered.

How to Pitch It (Stakeholders)

For executives: This is a small, free, unmaintained add-on that makes columns sortable in our internal Laravel Nova admin screens. The capability itself is basic and now built into Nova, so the package adds dependency risk without adding product value. Recommendation: do not adopt for new work; schedule removal from any legacy admin at the next Nova upgrade, at negligible cost and no customer impact.

For engineering: Treat ofcold/nova-sortable as legacy-only. It is MIT-licensed, last released October 2019, archived upstream, and low-adoption (32 stars), which means no upstream fixes for PHP/Laravel/Nova compatibility or security issues. Before any new adoption, confirm the exact behavior needed — if it is standard column sorting, use Nova's native sortable() support; if it is manual drag-ordering, implement a thin in-house trait plus a small Vue component so we own the code path. Action: inventory where it is loaded, pin or remove it, and add a note to the admin-panel upgrade checklist.