- What is lendo-stp-gdansk/lendo-cli-bundle?
- It is a vendor-authored Laravel/PHP CLI bundle from Lendo STP Gdańsk that ships reusable console commands and integrations for terminal-based development, automation, and operational workflows. It is operator tooling rather than a runtime library, so it belongs at the console edge of an application. There is no public evidence of community adoption, stars, or dependents, so treat it as an internal package that needs direct source review before use.
- Is lendo-cli-bundle a Laravel package or a Symfony bundle?
- That is the key unknown because the name says bundle but the target is Laravel projects. A true Symfony bundle would include Bundle registration, DependencyInjection extensions, and Resources/config YAML, while a Laravel package would ship a service provider with optional auto-discovery. Inspect composer.json and the source tree first, because the answer determines whether you need manual container wiring or standard Laravel package discovery.
- Which Laravel and PHP versions does lendo-cli-bundle support?
- Version support is not documented in the public metadata provided, so you must read the composer.json constraints for php, illuminate/support, and symfony/console. Laravel 10 and 11 pull Symfony Console 6.x, so an older bundle pinned to Console 5 will conflict. Confirm the matrix against your actual runtime before committing to adoption.
- How do I install lendo-cli-bundle in a Laravel application?
- Add it with Composer, then determine whether it uses Laravel package auto-discovery or requires manual provider registration. If it is Symfony-style, you may need to register the bundle or wire its services into the container yourself. After registration, run php artisan list and diff the command surface to see exactly what it exposes.
- What license does lendo-cli-bundle use?
- No license metadata is visible in the provided information, which is a blocking issue for production use. Check the repository LICENSE file and the license field in composer.json, then get legal sign-off before adopting. Without a clear license you cannot safely redistribute, fork, or vendor the code.
- Is lendo-cli-bundle safe to use in production?
- CLI commands often hold elevated privileges such as database writes, cache flushes, deploys, and data migrations, so an unvetted command bundle is an unvetted privileged surface. With zero stars, zero dependents, and an unclear license, there is no external validation of API stability or safety. Audit every command, pin to a commit SHA, and disable anything that touches infrastructure you do not control.
- What Artisan commands does lendo-cli-bundle provide?
- The exact command inventory is not publicly documented, so install it in an isolated environment and run php artisan list to capture the surface. Expect commands shaped around Lendo's environment conventions, such as bucket names, queue names, service endpoints, and credentials layout. Document each command and flag any that mutate production data or need elevated credentials.
- Are endpoints, credentials, and project names configurable in lendo-cli-bundle?
- This is unclear from the public description, but internal bundles frequently hardcode vendor-specific conventions. Review the source for config publishing, environment variables, and any hardcoded Lendo service endpoints or credential paths. Avoid sharing config keys with your own config namespace, and do not assume the commands will work against your infrastructure without changes.
- How should I test lendo-cli-bundle before adopting it?
- Run a time-boxed spike in a non-production Laravel app: register the provider or bundle, run php artisan list, and diff the command surface against what you need. Verify PHP, Laravel, and Symfony Console compatibility, then test each command against sandbox infrastructure only. If the spike succeeds, fork or vendor the repo, pin a commit SHA, and strip commands you do not need.
- What are the alternatives to using lendo-cli-bundle directly?
- Because this is greenfield adoption with no migration path, the stronger play may be to vendor the useful source into an internal tools package or rewrite a thin in-house command set. That keeps your own namespace, release cadence, and security review while preserving the utility. If you still consume upstream, isolate it as a console-only dev or ops dependency and avoid auto-discovery bleed into the HTTP kernel.