Weave Code
Support Laravel Package
sebwite/support
sebwite/support is a Laravel package that bundles handy support utilities and helper classes for everyday development. It reduces boilerplate, simplifies common tasks, and helps keep your application code cleaner, more consistent, and easier to maintain.
Laravel 5 support package
Frequently asked questions about Support
- What is sebwite/support used for?
- sebwite/support is a Laravel 5-era support package that bundles handy utilities, helper classes, base classes, and conventional ServiceProvider wiring. It is intended to reduce boilerplate and keep application code cleaner and more consistent. The assessment indicates it is likely a shared internal dependency of the Sebwite package suite rather than a standalone library.
- How do I install sebwite/support in a Laravel project?
- It is not distributed through Packagist, so you must add a Composer repositories entry pointing to the Bitbucket Git repository. You will likely need to require dev-master or pin an exact commit SHA, and every CI runner and developer machine needs credentialed access such as an SSH key or app password. For safer builds, mirror the repository into your own Git and publish it through a private Satis or Composer registry.
- Does sebwite/support work with Laravel 9, 10, or 11?
- No, the package is described as Laravel 5-era and is not a fit for modern Laravel targets such as Laravel 9, 10, or 11 on PHP 8.1 and above. Adopting it there would require a fork-and-port, and the assessment recommends treating it as a no-go without that work. For a legacy Laravel 5.x estate it may fit, but it still adds foundation-layer coupling.
- Which Laravel 5.x and PHP versions does sebwite/support support?
- The assessment identifies it as a Laravel 5.x package likely built for PHP 5.6 through 7.x, with possible coupling to specific Laravel 5.x minors. There is no evidence of tagged constraints, so you should inspect composer.json rather than assume broad compatibility. PHP 8 compatibility is not expected without code changes.
- Is sebwite/support actively maintained?
- There is no observable maintenance cadence, and the assessment flags a bus factor of one. The Bitbucket repository also creates availability and lifecycle risk because builds break if it is deleted or made private. With zero stars, zero dependents, and no community vetting, it should be treated as unmaintained unless you can confirm otherwise.
- What license does sebwite/support use?
- The provided material shows no evidence of a LICENSE file or a permissive license such as MIT or Apache. Without a clear permissive license, legal and compliance teams cannot approve adoption. Confirm licensing with the maintainer before using it in any production or commercial codebase.
- Does sebwite/support have tests, CI, or tagged releases?
- The assessment found no evidence of tests, CI, a CHANGELOG, or tagged releases. That likely means dev-master is the only installable constraint, which is a reproducibility hazard. If you must use it, lock to an exact commit SHA rather than a moving branch.
- Is sebwite/support safe to use in production?
- The technical risk is high: Laravel 5 is end-of-life, there is no upstream security patching, and unvetted code would execute with full application and container privileges. There is also no community CVE coverage or external signal that the code works outside its author's environment. Adopt it only for a legacy Laravel 5.x estate, and only after vendoring, auditing, and pinning it.
- Can sebwite/support conflict with other Laravel packages?
- Yes, a support package that registers global helpers, base classes, facades, or ServiceProvider bindings can collide with other packages and cause fatal redeclare errors. It may also override Laravel core bindings or Blade directives depending on what its providers register. Audit the provider boot code and helper declarations before adding it to an application with other dependencies.
- What are the alternatives to sebwite/support?
- The safest alternative is to reimplement the small set of helpers, traits, and base classes you actually use, since a support package's surface is usually limited. You can also rely on Laravel's built-in helpers and support classes where they cover the same need. If another Sebwite package hard-depends on it, fork and vendor it through a private registry instead of referencing Bitbucket directly.
Weaver
How can I help you explore Laravel packages today?