Nova Filemanager Laravel Package

Product Decisions This Supports

• Build vs. buy for admin file management. clevyr/nova-filemanager supplies a ready-made file browser (upload, rename, move, delete, directory navigation) inside Laravel Nova. Choosing it replaces an estimated multi-sprint internal build with a dependency + configuration task — a clear buy signal if you are already a Nova shop.
• Roadmap sequencing around Nova upgrades. This is a major version bump (4.x → 5.0.0) whose headline is "Nova 5.0 Support." That makes it a coupled upgrade: adopting Nova 5 forces this package to 5.x, and staying on Nova 4 means pinning to 4.1.1. It belongs on the Nova upgrade workstream, not as an independent line item.
• Feature scope for internal tooling. Relevant wherever non-technical operators (marketing, ops, content teams) need to manage assets on configured disks without SSH/SFTP. Not relevant to customer-facing upload flows — this is an admin-panel tool, not an end-user feature.
• Dependency risk register entry. v5.0.0's release note is a single line ("General house-keeping") plus a raw diff link. There is no enumerated changelog, no migration guide, no deprecation list. For a package that sits on an authenticated admin surface with filesystem write access, that is a maintenance-signal data point, not just a release note.

When to Consider This Package

Consider it when:

• You run Laravel Nova 5 and want file management in the admin panel without custom Vue/Inertia work.
• The requirement is human-driven asset management on one or more configured filesystem disks — not programmatic/API file operations.
• You accept Nova itself as a paid dependency; this package is an add-on to that decision, not a standalone one.
• You can pin versions and absorb a coupled Nova upgrade cycle in a planned maintenance window.
• Your team has PHP/Laravel capacity to read the source if documentation falls short — the terse changelog implies you will occasionally need to.

Look elsewhere (or hold) when:

• You are on Nova 4. Stay on 4.1.1; do not let a routine composer update drag you across a major boundary.
• You are not using Nova — the addressable surface is zero; a standalone tool (Flysystem-based browser, a dedicated DAM, or S3 console access) is the better comparison.
• You need enterprise support terms, SLAs, or a published security-response process. This is an agency-maintained package; treat it as community-grade.
• You require audit trails, granular per-role file permissions, or approval workflows — verify explicitly, as these are commonly out of scope for file-manager packages and would need to be built around it.
• You need rich media handling (transforms, CDN invalidation, virus scanning) as first-class features.

Before adoption, verify in a spike: the actual breaking changes in 5.0.0 (diff the tree or read commits, since the changelog won't tell you), Nova 5's platform floor (PHP/Laravel versions) against your stack, and whether existing disk/config files carry over unchanged.

How to Pitch It (Stakeholders)

To executives — one paragraph: We evaluated clevyr/nova-filemanager as a way to give operations staff a file-management screen inside our existing Nova admin panel without a custom build. The trade-off is favourable on cost — it's a small, focused package that replaces internal UI work — but it carries two governance caveats: it is version-locked to Nova's major releases (the new 5.0.0 exists solely to track Nova 5), meaning our Nova upgrade and this package's upgrade must ship together; and its release notes are thin, so we should pin the version, review changes before each bump, and not treat it as a supported vendor product. Recommendation: adopt, pinned, as part of the Nova 5 upgrade — not as an ad-hoc addition.

To engineering — the ask:

1. Pin explicitly. "clevyr/nova-filemanager": "^5.0" only on Nova 5; keep ^4.1 on Nova 4 branches. No floating constraints.
2. Read the diff before merging. "General house-keeping" is not a changelog. Confirm whether config keys, disk registration, authorization hooks, or publishable assets changed between 4.1.1 and 5.0.0.
3. Confirm platform floor. Nova 5 raises PHP/Laravel minimums; validate CI and production runtimes before scheduling the bump.
4. Isolate the surface. Ensure the file manager is gated behind Nova auth + policies, and that disks are scoped so an admin-panel tool cannot reach application-private storage.
5. Regression-test the write paths — upload, rename, move, delete, and path traversal handling — since these are the exact behaviours a "house-keeping" release could silently touch.

Open items for the next review: obtain a real changelog or diff summary for 5.0.0; record the package's last-commit and issue-response cadence as a maintenance-health metric; re-assess at the next major Nova release, which will be the next forced-upgrade event.