- What is lendo-stp-gdansk/lendo-infrastructure-bundle?
- It is described as an infrastructure bundle for Lendo STP Gdańsk Laravel applications. Its stated purpose is to package shared service providers, configuration defaults, HTTP clients, logging, and health-check wiring so teams can bootstrap services consistently. It is a platform standardization artifact rather than a typical feature package. You should review the source to enumerate exactly which providers, middleware, config keys, and outbound calls it includes.
- Is this a Laravel package or a Symfony bundle?
- The name uses Symfony's -bundle convention, while the description says it is for Laravel applications. Laravel has no native bundle concept, so the package may be a Laravel package that borrowed the naming, a Symfony bundle with a Laravel service provider bridge, or something intended for a mixed service landscape. Do not assume it drops into a standard Laravel app until you inspect composer.json and the source.
- Does it support Laravel package auto-discovery?
- This is not confirmed by the provided overview. Check composer.json for extra.laravel.providers and extra.laravel.aliases to see whether auto-discovery is configured. If those entries are absent, you will need to register the service provider manually or use a bridge. Verify this before planning integration work.
- Which PHP and Laravel versions does it support?
- Supported versions are not stated in the provided information. Inspect the composer.json PHP constraint and illuminate/* dependency constraints to determine compatibility with your stack. Also check whether the repository documents a supported-version policy or release cadence. Do not assume compatibility with current Laravel releases without verifying.
- How do I install lendo-stp-gdansk/lendo-infrastructure-bundle with Composer?
- The typical command would be composer require lendo-stp-gdansk/lendo-infrastructure-bundle, but confirm the package is available to your project first. If it is private or restricted, configure repository credentials or a path repository as appropriate. Review publishable config and migrations after installation. Pin a specific version rather than relying on an unpinned constraint.
- Is it safe to use this package in production?
- The technical assessment flags high ownership risk rather than proven code-quality risk. It is a single-vendor package with zero stars and zero dependents, so there is no community backstop, issue history, or external usage evidence. Version tags may be unpublished or yanked, and the license terms are unstated. Pin versions, review the source, and test in a low-risk service before broader adoption.
- Does it require Lendo internal services or network access at runtime?
- This is a key unknown. The assessment warns that the package may encode assumptions about Lendo's network topology, such as service discovery hosts, secret backends, or telemetry endpoints. Inspect config keys and service provider boot logic for outbound calls or container-build-time bootstrapping. If it registers global middleware or fails during boot, a defect could become an app-wide boot failure rather than a scoped one.
- What license is the package under and can I fork or vendor it?
- The license terms are not stated in the provided context. An internal package published to Packagist may still be proprietary, so confirm that you are permitted to consume, vendor, or fork it. Check the repository LICENSE file and any internal usage policy. Resolve this before committing to adoption or redistribution.
- Does the package have tests and CI, and how should I evaluate it?
- Test coverage and CI status are not confirmed by the provided overview. Check the repository for a test suite, CI configuration, and recent commit activity. Treat a hands-on source review as mandatory before commitment, and run smoke tests in a staging environment. Because there are no dependents, you cannot rely on third-party integration reports as evidence.
- Are there alternatives for correlation IDs, health checks, and structured logging in Laravel?
- Yes. The same cross-cutting concerns are available from maintained, widely adopted Laravel packages and framework features. Adopting this bundle mainly buys conformity with Lendo's operational conventions, not unique functionality. If your services do not need to interoperate with the Lendo platform, consider standard alternatives or wrap any Lendo-specific integration behind your own thin abstraction.