Weave Code
Lapresselibre Bundle Laravel Package
mediapart/lapresselibre-bundle
A Symfony bundle from Mediapart for integrating La Presse Libre content and services into your PHP application. It provides ready-made configuration and service wiring so you can pull La Presse Libre data with minimal setup. Lightly adopted, so expect limited docs and community support.
A Symfony bundle from Mediapart that packages integration with La Presse Libre, exposing the project's configuration and services to Symfony applications through the standard bundle/DependencyInjection workflow. Install it with Composer, register the bundle, and configure it via your application's config files.
- Standard Symfony bundle registration and container extension
- Configuration exposed through
Configuration/Extensionclasses - Autowired services ready for injection
- Compatible with the Symfony Flex recipe workflow
Frequently asked questions about Lapresselibre Bundle
- Is mediapart/lapresselibre-bundle a Laravel package?
- No. It is a Symfony bundle that wraps the mediapart/lapresselibre PHP library, and it contains a Bundle subclass, a dependency injection extension, and Symfony service and configuration definitions. There is no Laravel service provider, facade, config publisher, or illuminate/* constraint anywhere in it. Composer will install it into a Laravel application, but nothing will auto-wire because the bundle's entire value is Symfony-specific container compilation.
- Can I install mediapart/lapresselibre-bundle in Laravel 10, 11, or 12?
- Composer resolution will most likely fail before installation even completes. This is a 2017-era Symfony package, so expect PHP 5.6/7.0-7.1 and Symfony 2.8/3.x platform constraints, while modern Laravel requires PHP 8.1 or newer. Any transitive Symfony component pinned to 3.x also conflicts with dependencies already present in a current Laravel skeleton. Relaxing those constraints requires a fork, and even then the bundle still does nothing useful under Laravel.
- What does the bundle actually give me that the library does not?
- Only Symfony wiring: ready-made service definitions, a configuration tree, autoconfiguration tags, and DI extension glue. That value is entirely inert under Laravel's container, which resolves by type-hint and binds through ServiceProviders. For a Laravel team the bundle is best treated as reference documentation for how Mediapart constructed the underlying library, including constructor arguments, config keys, and service lifetimes. The realistic dependency is mediapart/lapresselibre itself.
- What PHP and Symfony versions does mediapart/lapresselibre-bundle require?
- Based on its 2017 release date and Symfony 2.8/3.x era, assume PHP 5.6, 7.0, or 7.1 constraints, though you should confirm by reading composer.json directly. It has not received PHP 8 compatibility work, so running it on a modern runtime is untested territory. Treat the exact platform requirements as unknown until you inspect the manifest of both the bundle and the library it wraps.
- What license is mediapart/lapresselibre-bundle released under?
- The repository is flagged as NOASSERTION, meaning GitHub could not match the license file to a known SPDX identifier. That suggests a custom, mixed, or otherwise non-standard declaration rather than a clean MIT or Apache header. Mediapart is a French newsroom with strong copyleft leanings, so AGPL is plausible, but you cannot assume it. Legal needs to read the actual license text and confirm compatibility with your distribution model before any code ships.
- Is mediapart/lapresselibre-bundle still maintained?
- No. The last release was on 2017-11-17, roughly eight years with no commits, releases, or security response. There is no CVE triage, no PHP 8 compatibility work, and no test or CI signal to lean on. Adoption is near zero at about 3 stars and 0 dependents, so there is no community, no forks with fixes, and no Stack Overflow corpus to consult.
- How do I integrate La Presse Libre into a Laravel application then?
- Consume mediapart/lapresselibre directly and demote the bundle to reference material. Define your own contracts, such as a DocumentProcessor interface, implement them with a thin adapter over the library, and bind the implementation in a ServiceProvider. If the dependency tree is not PHP 8 clean, fork and vendor the library into a private VCS repository, relax the platform constraints, and add characterization tests around the slice you actually use.
- Are there any maintained forks or alternatives to this bundle?
- Nothing meaningful surfaced in the evaluation: 0 dependents, no active forks carrying fixes, and no successor package identified under the Mediapart organization. That means every compatibility or security question becomes an internal investigation rather than a search. Before committing engineering time, check whether Mediapart has published a replacement and confirm how much of the library's surface area you actually need, since a small slice may be cheaper to reimplement.
- Does mediapart/lapresselibre-bundle perform network calls or need a companion service?
- That is not established and must be verified by inspecting the library, because the bundle only adds Symfony wiring around it. If the library is an external API client, your deployment shape changes and you inherit its authentication, retry, and timeout behaviour. If it is a parser, annotator, or document transformer, it can stay in-process. Resolve this question early, since it determines whether you need an outbound HTTP dependency or a background worker.
- Is mediapart/lapresselibre-bundle safe to run in production?
- Not as shipped. Unmaintained code is unexamined code: there is no security scan history, no CVE triage since 2017, and unknown transitive dependency age. Combined with an unresolved NOASSERTION license, this is a hard blocker rather than a footnote for a production newsroom or publishing system. If you proceed, isolate the library behind your own interface, pin and audit the dependency tree, and be prepared to own it permanently.
Weaver
How can I help you explore Laravel packages today?