- Can I use spaceheadlabs/ssh-bundle in a Laravel application?
- Not as a native Laravel package. The repository is a Symfony bundle that ships a Bundle class, DI extension, and compiler passes, so there is no Laravel service provider or bundle lifecycle to hook into. The practical approach is to treat its plain PHP service classes as a reference and bind your own SSH client implementation in a Laravel service provider.
- How do I install spaceheadlabs/ssh-bundle with Composer?
- You would install it with composer require spaceheadlabs/ssh-bundle, but the technical assessment recommends against adding it as a runtime dependency for a Laravel app. Before any install, check composer.json for the PHP constraint, Symfony version range, and license. The bundle is designed for Symfony kernel registration, so installation alone will not wire it into Laravel's container.
- What does spaceheadlabs/ssh-bundle use under the hood for SSH connections?
- The assessment could not confirm this from the available metadata. It almost certainly wraps phpseclib/phpseclib or ext-ssh2, but a shell-out to the ssh binary is also possible and would be disqualifying for most use cases. Audit the source and composer.json before relying on it, because the underlying transport determines portability, key handling, and timeout behavior.
- Does spaceheadlabs/ssh-bundle support Laravel 10 or Laravel 11?
- There is no evidence of explicit Laravel 10 or 11 support. Because it is a Symfony bundle, it depends on Symfony components and a kernel lifecycle that Laravel does not provide. Its PHP and Symfony constraints may also conflict with the Symfony 6 or 7 components shipped with recent Laravel versions, so verify compatibility before considering it.
- Is spaceheadlabs/ssh-bundle safe to use in production with private keys?
- Treat it with caution. The package has zero stars, zero dependents, and no observable production validation, which is a poor position for a component that handles private keys and remote shell access. Check whether host key verification is enforced by default, whether passphrase-protected keys are supported, and whether there is any security disclosure process before using it.
- How do I configure SSH hosts and credentials with spaceheadlabs/ssh-bundle?
- Configuration in the bundle follows Symfony's tree-based config definitions rather than Laravel's config publishing model. The assessment notes named connections, config-driven hosts, credential handling, and a command runner as the likely abstraction shape. In Laravel you would need to replace that with a flat config/ssh.php file and your own connection factory.
- Can spaceheadlabs/ssh-bundle capture stdout, stderr, and exit codes?
- Yes, capturing stdout, stderr, and exit codes is listed among the package's features. The fluent API is intended to run single or multiple remote commands and inspect the output. Test the failure paths yourself, because the assessment flags auth failure, timeout, and host-key verification as the areas SSH wrappers most often get wrong.
- Does spaceheadlabs/ssh-bundle support SFTP or file uploads?
- SFTP support is not confirmed in the provided description. The assessment lists upload and download as operations to look for, but whether the bundle provides SFTP helpers depends on the underlying library and must be verified in the source. If file transfer is a requirement, confirm it directly rather than assuming.
- What are the best alternatives to spaceheadlabs/ssh-bundle for Laravel?
- Use phpseclib/phpseclib directly and bind a narrow SshClient interface in a Laravel service provider. Define only the operations you need, such as execute, upload, download, and disconnect, and publish a flat config/ssh.php. That approach avoids the Symfony impedance mismatch and gives you full control over host key verification, timeouts, and connection pooling.
- Is spaceheadlabs/ssh-bundle actively maintained and tested?
- The available signals are weak. Zero stars, zero dependents, and a low composite score indicate no downstream validation, and the assessment asks whether the last commit is within 24 months and whether any test suite exists. It also questions whether SpaceheadLabs intends to maintain the package, so assume you will own any code you extract.