Phpamo Laravel Package

Product Decisions This Supports

• Mixed-content remediation for legacy content. If any part of the product renders user-supplied or imported image URLs (http:// avatars, marketplace listings, RSS/email ingest, CMS migrations), Camo lets you serve them over HTTPS without a data backfill. This package is the URL-signing piece that makes that render path work.
• Privacy / IP-leak reduction. Proxied images hide end-user IPs and referrers from third-party image hosts — a defensible answer to security reviews and privacy questionnaires, and relevant for GDPR-adjacent diligence.
• Build vs. buy scoping. The package is thin: it constructs a signed Camo URL (HMAC over the target URL plus hex encoding). Treat it as a reference implementation, not a strategic dependency. The real build/buy decision is the Camo service itself (self-hosted Go binary, ops ownership, cache sizing), not this library.
• Roadmap framing. This is infrastructure hygiene, not differentiation. Scope it as a small platform utility behind an internal ImageProxy interface so the vendor can be swapped later without touching feature code.
• Concrete use cases: hardening an HTTPS storefront with inherited http:// product images; proxying third-party avatars; rendering email/PDF templates that must not leak recipient IPs; throttling hotlink-heavy UGC.
• Explicit non-goals. The package does no fetching, caching, resizing, or format conversion. Do not let stakeholders infer image-optimization benefits from it.

When to Consider This Package

Consider it when:

• You already run — or have approved running — a Camo instance and only need signed URL generation from PHP.
• You are on PHP 7.x, or you have verified PHP 8.x compatibility yourself (last release 2020-04-21; no declared support for modern Laravel).
• You need a signed-URL helper and want a MIT-licensed starting point rather than a maintained SDK.
• Your need is narrow and stable: the Camo URL contract is unlikely to change, so low maintenance activity is tolerable.

Look elsewhere when:

• You need transformations, responsive variants, or CDN edge caching — evaluate imgix, Cloudinary, Cloudflare Image Resizing, or Glide/Intervention.
• You cannot operate a proxy service; a managed proxy removes the ops burden this package assumes.
• You can simply require HTTPS image sources — the cheapest fix is validation at ingest, not a proxy.
• Your stack is Laravel 10/11 on PHP 8.2+. Budget for forking and vendoring; at 42 stars and a single maintainer, do not expect upstream fixes.
• You need active security response or a support contract — this is a volunteer project with a stale release.

How to Pitch It (Stakeholders)

To executives: We can eliminate browser mixed-content warnings and stop leaking customer IPs to third-party image hosts without re-processing years of stored content. The library is MIT-licensed and free; integration is roughly one to two engineering days. The cost is operational, not licensing — we would run a small image-proxy service, which is the same requirement for any proxy approach. Position it as a security and privacy checkbox, not a product feature.

To engineering: willwashburn/phpamo is a framework-agnostic Composer package that signs Camo URLs; it has no Laravel coupling and a tiny API surface. Two caveats: the last release predates PHP 8.2, so verify compatibility in a spike and pin or vendor the dependency; and the package is deliberately minimal, so wrap it behind an internal interface. Maintenance risk is low precisely because the signing logic is trivial — worst case we reimplement it in a service class.

The ask: approve a short spike to (1) confirm PHP 8.x compatibility, (2) decide self-hosted Camo vs. a managed image proxy, and (3) scope ingest-time validation of image URLs as the cheaper alternative where it applies.