Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Kayue Essence Bundle

Kayue Essence Bundle Laravel Package

kayue/kayue-essence-bundle

Symfony bundle integrating Essence, a PHP library for extracting media and metadata from web pages. Fetch titles, descriptions, images, and embedded media via Open Graph, Twitter Cards, oEmbed, and other providers—useful for link previews and content cards.

View on GitHub
Deep Wiki
Context7

This bundle integrates the Essence library (an oEmbed library) into Symfony 2.

Frequently asked questions about Kayue Essence Bundle
Can I install kayue/kayue-essence-bundle in a Laravel application?
No. kayue/kayue-essence-bundle is a Symfony 2 bundle, not a Laravel package; it ships a Bundle subclass and a Symfony DI extension with no Laravel equivalent, and its PHP 5.x-era constraints will likely fail Composer resolution against Laravel 10 or 11. For Laravel, target the underlying essence/essence library and wrap it in your own service provider.
What is the difference between kayue-essence-bundle and essence/essence?
The bundle is a thin Symfony 2 integration layer that registers Essence as a container service and exposes DI parameters. essence/essence is the framework-agnostic library underneath it, handling oEmbed provider discovery, HTTP transport, and caching. Laravel adoption should target the library, using the bundle only as a reference for provider configuration.
How do I integrate Essence media extraction into Laravel?
Require essence/essence with Composer after checking its PHP and Guzzle constraints against your Laravel version. Create a small service provider that binds Essence\Essence as a singleton, supply a Guzzle 7 or Laravel HTTP client adapter, and add a Laravel Cache-backed adapter for oEmbed responses. Port the bundle's provider configuration by hand—it is typically tens of lines, not a migration project.
Which Laravel and PHP versions does kayue-essence-bundle support?
There is no supported Laravel version because this is a Symfony 2 bundle, not a Laravel package. Its constraints are PHP 5.x-era and Symfony 2 reached end of maintenance in January 2019, so it is not suited to Laravel 10 or 11 on PHP 8.2+. Check essence/essence directly for its current PHP and framework-compatible constraints.
How do I configure HTTP client options for Essence in Laravel?
The bundle's Symfony DI configuration does not carry over to Laravel. Instead, configure HTTP behavior in the adapter you bind into the container, setting timeouts, headers, user agent, and retry policy on Guzzle 7 or the Laravel HTTP client. Pair it with a cache adapter that respects a TTL policy for oEmbed responses.
Is kayue-essence-bundle still maintained?
There is no evidence of active maintenance: the bundle has roughly 6 stars, no dependents, a single maintainer, and no visible CI. Symfony 2 is long past end of life, and the dependency constraints are stale. Treat it as an unmaintained dependency and a reference implementation rather than something to install in production.
What can Essence extract from a URL?
Essence extracts media metadata from supported URLs, including titles, descriptions, thumbnail images, embed URLs, and provider details. It works through Open Graph, Twitter Cards, oEmbed, and other provider mechanisms. In a Laravel app this is useful for link previews, content cards, and rich embeds for known providers such as YouTube, Vimeo, and Twitter.
What are alternatives to kayue-essence-bundle for Laravel?
The most direct alternative is essence/essence wrapped in a Laravel service provider with your own HTTP and cache adapters. You can also evaluate embed/embed, a first-party or provider-specific oEmbed client, or SDKs for the specific providers you support. Choose an option with active maintenance and constraints that match your PHP and Laravel versions.
How do I test Essence integration in Laravel?
Write feature tests around your service provider using recorded HTTP fixtures so tests do not hit live providers. Fake the HTTP client to assert adapter behavior, and cover metadata extraction, cache hits and TTL, URL validation, and provider allowlisting. Include a failure-path test for unsupported or malicious URLs.
What security concerns should I consider when fetching media metadata?
Fetching arbitrary URLs introduces SSRF risk, so validate schemes and hosts and enforce an allowlist of supported providers. Sanitize extracted titles, descriptions, and embed HTML before rendering to prevent HTML injection, and set strict HTTP timeouts. Because the bundle is unmaintained, put any dependency through a security review and document a fork-or-replace trigger.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo
bernskioldmedia/laravel-harvest
bernskiold/laravel-data-scrubber
bernskiold/laravel-currency-converter
bernskiold/laravel-campaign-monitor
bernskioldmedia/laravel-autotranslate
siberfx/telegram-bot
roy-sandip/laravel-view-extended
gregsphotography/site-builder-core
roy-sandip/laravel-view
anodyne/blade-fluentui-icons
webx-ui/module-catalog-collections