Assetic Cache Busting Worker Bundle Laravel Package

Product Decisions This Supports

• Cache-busting / asset fingerprinting strategy. The bundle's only job is to register Assetic's CacheBustingWorker in the DI container so compiled assets get a content hash in the filename (e.g. app.a1b2c3d4.css). That is a real product decision — long-lived CDN/browser caching with immutable filenames — but this package is only the wiring, not the mechanism.
• Framework fit check — correct the premise. This is a Symfony bundle, not a Laravel package. If your roadmap is Laravel, this package is irrelevant: Laravel's equivalents are Mix/Vite manifest hashing or elixir-era version(). Do not let the "PHP package" label pull it into a Laravel build-vs-buy comparison.
• Build vs. buy (really: inherit vs. replace). With 2 stars, 0 dependents, last release 2016-03-09, and an archived repo, "buy" is not on the table. The decision is whether to keep an inherited dependency or spend a sprint removing it.
• Roadmap signal, not a feature. The package's existence in your dependency tree is evidence that the app is on Assetic, which itself is effectively end-of-life in the Symfony ecosystem (superseded by Webpack Encore, then Symfony AssetMapper from 6.3). Treat adoption as a trigger to schedule an asset-pipeline migration rather than a decision in its own right.
• Concrete use case where it earns its keep: a Symfony 2.x/3.x application already running Assetic, already using the cache-busting worker, and needing the bundle merely to avoid hand-writing service definitions. Expected effort to replace the bundle's value in-house: an afternoon — it is a thin container-configuration shim.

When to Consider This Package

Consider it only when all of the following hold:

• The application is Symfony (2.x/3.x era) and already committed to Assetic as its asset pipeline.
• You are already using assetic/cache-busting-worker and just want the Symfony bundle glue.
• The codebase is frozen or in maintenance-only mode, with no near-term framework upgrade.
• You have accepted that no security or compatibility patches will arrive.

Look elsewhere — decisively — when:

• The stack is Laravel. Different pipeline entirely; this package contributes nothing.
• The Symfony version is 4.x or newer. Use Webpack Encore; on 6.3+ use AssetMapper with symfony/asset versioning, which gives content-hashed filenames natively and is maintained.
• You need a supported dependency. Archived repo, ~decade-old release, no maintainer, and PHP/Symfony version constraints that will not resolve against modern Composer graphs without --ignore-platform-reqs hacks.
• You need more than hashing — integrity hashes (SRI), preloading, CDN invalidation hooks, or per-environment manifests. None of that is here.
• Any signal of active product investment. A 0.1 score and 2.16 opportunity score reflect a package with essentially no forward value; adopting it creates debt, not leverage.

How to Pitch It (Stakeholders)

To executives: Do not adopt this. It is an archived, unmaintained Symfony bundle from 2016 with two stars and zero downstream dependents, used to add a content hash to compiled asset filenames. The capability it provides — cache-busting so browsers and CDNs fetch new assets after a deploy — is genuinely important, but this is not the way to get it in 2024. Its presence in a codebase is a signal that the app sits on Assetic, an asset pipeline the Symfony community has moved past. Recommend funding a short migration to a supported pipeline rather than a dependency on an unmaintained one; the security and upgrade risk outweighs the negligible integration savings.

To engineering: This is a container-configuration shim around assetic/cache-busting-worker — it registers the worker so Assetic writes content-hashed filenames. Low complexity, low risk to remove, and effectively zero cost to replicate if some legacy path truly needs it. For anything greenfield or Laravel-based, close the ticket: wrong framework, wrong decade. For legacy Symfony, put it on the decommission list alongside Assetic itself and pair the removal with the move to Encore or AssetMapper.