- What does aerni/imagekit do?
- It is a Statamic addon that provides a simple way to generate ImageKit delivery URLs from an endpoint, a transformation string, and an asset path. It is intentionally narrow: it does not add a data model, storage layer, service abstraction, queue, or event surface. In practice, it is a convenience wrapper for composing CDN-backed image URLs in Statamic templates.
- Is aerni/imagekit a Laravel package or a Statamic addon?
- Although it may be described as a Laravel/PHP package, the repository is a Statamic addon that sits in Statamic's addon and tag layer. It only fits stacks already running Statamic on Laravel. For a plain Laravel service, Symfony app, or headless setup, the package does not provide a meaningful integration point.
- How do I install aerni/imagekit?
- Installation is the normal Composer flow: require aerni/imagekit and register the addon/provider and any tag you need. The real gate is version alignment, because the last release was in August 2020 and Statamic addon bootstrapping and tag signatures have changed since then. Validate the install in a scratch Statamic instance before adding it to a real project.
- Which Laravel and Statamic versions does aerni/imagekit support?
- The provided context does not include an official compatibility matrix. The last release date, 2020-08-28, places it in the Statamic 2 / early Statamic 3 era, so expect breakage on Statamic 4.x and 5.x. Pin and test the exact PHP, Laravel, and Statamic combination in a spike branch before relying on it.
- Can I use aerni/imagekit in a plain Laravel app without Statamic?
- Not usefully. The package is a Statamic addon, not a general Laravel ImageKit client, and its value is in the Statamic tag/addon integration for URL composition. Outside Statamic, use ImageKit's official PHP SDK plus a small internal URL builder, or copy the URL-composition convention into your own code.
- Is aerni/imagekit still maintained?
- The context points to an unmaintained package: last release in August 2020, a single maintainer, two stars, zero dependents, and no releases for roughly five years. That means no community to catch regressions and no upstream owner to ship fixes for Statamic changes or ImageKit API updates. Treat it as a frozen dependency or a reference implementation rather than a safe long-term runtime dependency.
- How does aerni/imagekit build ImageKit URLs?
- It composes an ImageKit delivery URL from three parts: the endpoint, a transformation string, and the asset path. The package does not appear to model assets, storage, or uploads in the way a full SDK would; its core is the URL-composition convention. That is also why reimplementing the same logic in-house is often cheaper than patching the addon.
- Does aerni/imagekit support signed URLs, private images, or responsive srcset?
- The package is described narrowly as generating ImageKit URLs, and the evaluation explicitly questions whether you need signed/private URLs, responsive srcset generation, or cache invalidation beyond public URL generation. There is no indication in the provided context that it tracks ImageKit's newer named transformations, signed URLs, or query-parameter overrides. Confirm those requirements against ImageKit's current API before choosing this addon.
- What should I use instead of aerni/imagekit?
- For a plain PHP or Laravel application, the safer primitive is ImageKit's official PHP SDK plus a thin URL builder you own. For Statamic projects, copy the addon's small URL-composition logic into your own namespace, add tests, and register your own tag if needed. The evaluation recommends treating the repository as a reference implementation and dropping the Composer dependency.
- Is aerni/imagekit safe to use in production?
- The security surface is low because the package mainly builds URL strings, but the operational risk is high: it is abandoned, untested against current Statamic versions, and not tracking ImageKit API changes. A production adoption should include a fork-and-patch owner and a documented fallback to origin URLs. The default recommendation is to reimplement the URL builder and remove the dependency from your audit and upgrade surface.