Pyrocms Theme Laravel Package

Product Decisions This Supports

• Deprecation triage, not feature selection. This package is explicitly marked DEPRECATED and superseded by the Accelerant theme. Its only real product value is as an input to a "what do we do with our legacy PyroCMS footprint?" decision — retire, migrate, or freeze.
• Build vs. buy: neither. There is no buy case (1 star, 0 dependents, no maintenance signal) and no build case (you would not fork a deprecated admin theme for a Laravel product). The decision it supports is substitution: Accelerant, or a maintained Laravel admin panel.
• Roadmap hygiene. If this appears anywhere in a dependency graph or an old spec, that is a signal of stale requirements — a candidate for a cleanup ticket rather than a roadmap item.
• Migration scoping. For teams still on a pre-Accelerant PyroCMS release, the package is useful as reference material for understanding the legacy admin markup and CSS conventions that a theme migration must preserve or replace.
• Vendor-risk precedent. A concrete example to cite when justifying a policy like "no dependencies below a maintenance threshold" or "abandoned packages require an owner and an exit plan."

When to Consider This Package

Consider it only in narrow, backward-looking situations:

• You are maintaining a legacy PyroCMS installation pinned to this theme and need to read its source to understand rendering, view overrides, or asset conventions before migrating.
• You are archaeologically reconstructing an old admin UI for a migration, audit, or documentation effort and want the original reference implementation.
• You are evaluating PyroCMS's historical theming model to justify a platform choice (e.g., "this is why we moved to a maintained admin panel").

Look elsewhere — decisively — when:

• You need a maintained admin theme. Use Accelerant if you are on PyroCMS at all; use a maintained Laravel admin solution (Filament, Nova, Backpack, or similar) otherwise.
• You require security patches, PHP/Laravel version compatibility, or vendor support. None of that is on offer here.
• You are starting anything new. A deprecated package with zero dependents is not a foundation.
• You need community answers, examples, or third-party integrations. At this scale, there is effectively no ecosystem to lean on.

Before any adoption decision, verify the current state directly: the deprecation notice, the abandonment flag on Packagist, Composer/PHP version constraints, and the last commit date. The description already answers the question, but a PM should confirm rather than inherit the claim.

How to Pitch It (Stakeholders)

To executives: This is a dead-end dependency. It is the former official admin theme for PyroCMS, formally deprecated and replaced by Accelerant, with negligible adoption and no maintainer activity. I am recommending no adoption and no budget allocation. The strategic value is as a cautionary data point: if it shows up in a proposal or an existing codebase, that indicates stale requirements or accrued technical debt, and the right response is a migration ticket — not an investment. Cost of doing nothing is low; cost of building on it is a fork-and-own obligation with no upstream.

To engineering: Do not install. It is deprecated in favor of Accelerant, sits at one star and zero dependents, and carries no maintenance commitment. If you encounter it transitively in a legacy PyroCMS app, treat it as technical debt with an owner and an exit date, and scope the migration to Accelerant — or off PyroCMS entirely — as part of the next platform cycle. If you need reference material for the legacy theme layer during that migration, read the source; do not vendor it. Where a maintained admin UI is the actual requirement, evaluate Filament or an equivalent against our Laravel version and support expectations rather than retrofitting a deprecated theme.