- What is smorken/support and what does it do?
- smorken/support is described only as "Support classes for Laravel," a collection of reusable helper utilities intended to reduce boilerplate in Laravel applications. The provided context does not list the exact classes, traits, helpers, or service providers it exposes, so audit the Bitbucket source before adopting it. Treat it as a candidate source of isolated helpers rather than a platform dependency.
- How do I install smorken/support in a Laravel application?
- Because the package appears to be hosted on Bitbucket rather than Packagist, install it through a Composer VCS repository entry and require the package by name. You will need Bitbucket credentials available in developer environments and CI/CD. Start in a sandbox and pin an exact commit or tag, since no releases or version constraints are visible.
- Is smorken/support available on Packagist?
- The context indicates the repository is on Bitbucket and does not show a Packagist listing. That means Composer will not find it through normal Packagist resolution unless it has been published there separately. Plan to configure a VCS repository and manage credentials instead.
- Which Laravel and PHP versions does smorken/support support?
- The provided information does not show Composer constraints, a CI matrix, or documented Laravel and PHP version support. Compatibility is therefore unknown until you inspect composer.json and run a test matrix against your current and next Laravel/PHP versions. Check autoloading, service-provider discovery, facade aliases, and global helper collisions during that validation.
- Does smorken/support have tests, CI status, or documentation?
- The context reports no visible tests, CI status, tags, release notes, or documentation beyond the short description. That absence is a risk because you cannot rely on automated checks or documented upgrade paths. Run static analysis and unit tests internally before using any class in production.
- Is smorken/support safe to use in production?
- It carries high technical risk relative to value: zero stars, zero dependents, no visible community validation, unclear license, and a single Bitbucket repository. If you adopt it, wrap usage behind an internal adapter or vendor only the specific classes you need. Roll out behind a feature flag and review after one release cycle.
- Does smorken/support register service providers, facades, or global helpers?
- The context does not confirm what the package registers; it explicitly flags undocumented global helpers, facades, config, and service-provider side effects as risks to check. Inspect the source and composer.json for Laravel package discovery and helper autoloading. Avoid adopting broad service-provider behavior unless it provides clear, unique value over Laravel-native utilities.
- What license governs smorken/support?
- The provided information says the license is unclear and recommends a source and license audit before adoption. Do not assume you can modify or redistribute it until you confirm the license in the repository. If the license permits, consider forking or mirroring internally with attribution.
- How do I update smorken/support if it has no version tags?
- Without semantic version tags, upgrades become commit-diff reviews rather than normal Composer version bumps. Pin an exact commit in composer.json, mirror or fork the repository internally, and assign an internal owner for updates. Document adopted behavior and maintain a fallback in case the Bitbucket repository changes or disappears.
- Should I use smorken/support or Laravel's built-in helpers instead?
- Prefer Laravel-native utilities unless smorken/support offers a discrete, stateless helper with clear, measurable value. Because the package has no visible community validation or documentation, copying a few useful classes into an internal support package may be safer than adding a direct external dependency. Keep any external usage behind internal interfaces so it can be replaced later.