Weave Code
Uranus Laravel Package
lara-zeus/uranus
Uranus is a Laravel package in the Lara Zeus family, giving you ready-made building blocks for admin panels and back-office apps. Drop it into an existing Laravel project, tweak a few config options, and start shipping polished screens faster.
convert any admin panel to filamentphp
Frequently asked questions about Uranus
- What does lara-zeus/uranus actually do?
- The package is described as converting an existing admin panel to Filament, but its bundled description reads more like a generic config-publishing Laravel package with a service provider and Blade output. Those are two different products with two different blast radii, and the ambiguity is unresolved in the public documentation. Read src/ and composer.json before assuming which one you are getting.
- How do I install lara-zeus/uranus?
- The mechanical path is composer require lara-zeus/uranus, then rely on package discovery, publish the config and assets, and register the plugin on a Filament panel provider. Installation is almost certainly trivial; the real feasibility question is whether you can own it afterward. Because the repository is archived, there is no upstream to return defects to.
- Is lara-zeus/uranus still maintained?
- No. The repository is archived, the last release was 2024-04-01 (v1.0.0), it has roughly 15 stars and 0 dependents, and there is no upstream to ship fixes or compatibility work. Treat abandonment as the starting condition rather than a risk to monitor, and plan accordingly.
- Which Laravel and Filament versions does lara-zeus/uranus support?
- That is not documented publicly: there is no CI matrix, and the changelog is auto-generated with no features, breaking changes, or migration notes. Given the April 2024 freeze, it is likely pinned to a single Filament major, which caps your upgrade path from the day you adopt it. Check the declared php, laravel/framework and filament/filament constraints in composer.json.
- Should I use lara-zeus/uranus in production?
- Not as a runtime dependency. The two defensible uses are a time-boxed read-only spike to harvest patterns, or a deliberate fork with a named internal owner and a business case written against total cost of ownership. If the answer to 'who fixes this when Filament ships its next major' is 'we do, indefinitely', it is a fork evaluation rather than a dependency evaluation.
- Does lara-zeus/uranus modify my existing admin panel code?
- Unclear, and that is the blocking issue. If it is genuinely a conversion or codegen tool, it can leave a partially converted panel, which is materially worse than a broken page and much harder to roll back because the artefact is your own modified codebase. If it is only a config-and-Blade package, the blast radius is far smaller. Resolve this before scoping any pilot.
- Does lara-zeus/uranus have a test suite or CI?
- No verification surface is published: no CI matrix, no coverage claims, and a v1.0.0 changelog that lists no features or migration notes. Every capability claim is a hypothesis until you read it from source. Budget time for a source audit before committing to anything.
- Can I use lara-zeus/uranus with Inertia, React, or Vue?
- No. Uranus targets the TALL stack with Blade and Tailwind output and exists to move an admin panel onto Filament. If your front end is Inertia/React/Vue-first, or your back end is not Laravel, the integration cost exceeds any notional saving before code quality is even considered.
- What are the alternatives to lara-zeus/uranus?
- Build directly on Filament's own panel builder and official plugins, since Filament is the platform decision and Uranus is a satellite of it. Other Lara Zeus packages cover adjacent back-office building blocks if you want ready-made scaffolding. Keep the Filament version choice explicit rather than letting a 15-star archived package act as a proxy for it.
- Who maintains lara-zeus/uranus if I fork it?
- You do. The repository is archived with no advisory feed and no compatibility work for future Laravel or Filament majors, so a fork needs a named internal owner and a maintenance budget. Also check whether any transitive dependency pulls in a second abandoned package before you commit.
Weaver
How can I help you explore Laravel packages today?