- What is awcodes/trov and what does it do?
- Trov is presented as a Laravel and Filament starter kit for adding CMS functionality to websites. It includes a service provider, publishable config, Eloquent-backed content models, and Filament resources and pages. Treat it as a scaffold to read and own rather than a drop-in utility, and verify the source because available descriptions are inconsistent.
- Is awcodes/trov still maintained?
- No. The repository is archived, the last release is 2022-08-01, and v0.3.7 is the terminal artifact. Archival means no fixes, security patches, or Laravel and Filament version-range updates are coming, and there is no upstream issue channel for escalation.
- Can I use Trov with Laravel 11 or Laravel 12?
- Almost certainly not without changes. A mid-2022 Filament package will carry Filament 2.x and Laravel 9-era constraints, so current Laravel 10 through 12 and modern Filament are likely outside its declared ranges. Expect Composer resolution to fail before runtime, and plan for version pinning or a port.
- Which Filament version does Trov require?
- Trov is from the Filament 2.x era, so current Filament releases are likely outside its Composer constraints. Check the package composer.json rather than assuming, because the first blocker is usually dependency resolution. Also note that v0.3.7 moved auth-related items to awcodes/filament-sentry.
- How do I install awcodes/trov?
- The normal path is composer require awcodes/trov, publish the config, and run migrations, but on a modern Laravel and Filament app that may not resolve. If it installs at all, expect to pin older framework versions or patch the package. For planning, treat install-and-use as unavailable and plan a read-and-port work package.
- Is Trov safe to use in production?
- It carries high technical risk because it is archived and unmaintained. There are no security patches, framework-drift fixes, or upstream support, and zero dependents means little field evidence. Using it as a dependency in production is hard to justify; porting selected code into your own app is the safer framing.
- Does Trov handle authentication and permissions?
- Not self-contained. v0.3.7 moved auth-related items out to awcodes/filament-sentry, so authentication scope is not fully in the kit. Any admin visibility or permission behavior becomes your explicit design decision and your code to write.
- Is Trov a Composer package or a starter kit to clone?
- The available material is ambiguous: it is described as a CMS scaffold, a lightweight utility with an expressive API, and in some places as an unrelated Sentry and Filament plugin. Resolve this by reading the source before estimating. Practically, plan against a scaffold you clone or port and own, not a maintained dependency.
- How should I evaluate Trov before adopting it?
- Start by reading the source and its composer.json constraints, then try installing it in a throwaway Laravel 9 and Filament 2 app. Run Composer why-not checks against your target stack to see the exact conflicts. Any estimate should be traceable to someone who has read the code, not secondhand summaries.
- What are alternatives to Trov for Laravel CMS work?
- The safer route is a maintained Filament panel with custom Eloquent content models and resources, or a currently supported Laravel and Filament CMS starter kit. Trov can still be useful as reference code for content modeling and admin screens. Avoid adopting it as a long-lived dependency because the repository is archived with no dependents.