Lastfm Bundle Laravel Package

Product Decisions This Supports

This is a Symfony bundle (not a Laravel package) that wires the Last.fm web API into a Symfony application through DI-configured services. For a PM it informs:

• Build vs. buy for music/social-listening features. If the roadmap includes Last.fm integration — scrobbling, listening history, artist/track metadata, similar-artist data — this bundle eliminates the HTTP-client and service-wiring work. The product value is plumbing, not capability.
• Scope boundaries. It is integration glue only. It does not supply UI, caching policy, rate-limit handling, session-key/user-auth flows, or recommendation logic. Those remain product and engineering work regardless of adoption.
• Stack fit as a gating decision. For Laravel-first organizations this is the wrong dependency; the DI/bundle model adds friction. A thin PSR-18 client or a Laravel-specific package is the better build decision.
• Dependency risk posture. 1.5.0 is maintenance-only: 8 PRs, 0 issues, no new API surface, no feature velocity. Treat it as a stable utility, not a strategic dependency — wrap it behind your own adapter so it can be swapped.
• Platform planning. 1.5.0 drops PHP 8.2 support, so adoption/upgrade requires the runtime floor to be ≥8.3. Budget that upgrade before scheduling work.

When to Consider This Package

Adopt when:

• The application is on Symfony (6/7-era) and standard Last.fm API access is needed without hand-rolling HTTP and DI wiring.
• PHP is already at 8.3+; 1.5.0 removes 8.2 support, making this a prerequisite rather than a follow-up.
• The team can own the product layer: user auth/session keys, UX, caching, retry/rate-limit policy.
• Last.fm is a supporting integration, not a core revenue path.

Look elsewhere / do not adopt when:

• The codebase is Laravel — the Symfony bundle and DI model are a poor fit; prefer a PSR-18 client or Laravel-native package.
• You need an evolving feature roadmap, SLA, commercial support, or guaranteed maintenance; this is volunteer-maintained OSS.
• Last.fm is business-critical — no vendor backing means the dependency should be isolated behind an internal interface with an exit path.
• You are pinned to PHP 8.2 or older tooling, or rely on Psalm/Infection in CI (both removed from this project's pipeline, signaling tooling direction only — not a downstream constraint).

How to Pitch It (Stakeholders)

Executives: A small, free open-source Symfony integration for Last.fm. It removes integration plumbing but delivers no differentiated product capability — the listening/music features still require product design and engineering. Cost is low, lock-in is low if abstracted, and there is no vendor relationship to manage. The 1.5.0 release is housekeeping: no new functionality, just dependency bumps and a raised PHP floor (8.2 support dropped).

Engineering: Standard Symfony bundle exposing DI-configured Last.fm services. 1.5.0 is maintenance-only — PHP 8.2 dropped (runtime now ≥8.3), PHPUnit 12, PHPStan 2, Psalm replaced by PHPStan, Infection removed from CI. No API changes. Safe minor upgrade once the PHP version is confirmed; consume it behind an adapter so the Last.fm dependency stays swappable and the product layer (auth, caching, rate limits) remains ours.