Weave Code
Core Laravel Package
tether/core
Tether Core supplies foundational building blocks for Laravel projects: shared service providers, helper utilities, and configuration scaffolding that keep packages consistent. A lightweight base layer for teams building modular applications.
At a glance
Frequently asked questions about Core
- What is tether/core used for in a Laravel application?
- Tether Core provides foundational building blocks for the Tether Laravel ecosystem: shared service providers, configuration, contracts, base classes, and lightweight utilities. It is intended to keep dependent Tether packages consistent without duplicating boilerplate. It is not a feature package itself, so evaluate it as plumbing your application or sibling packages depend on.
- How do I install tether/core with Composer?
- Install it with composer require tether/core. The package ships an auto-discovered service provider, so you normally do not register it manually in config/app.php. Config publishing is optional and should be done only after you confirm the package's version constraints match your Laravel version.
- Which Laravel and PHP versions does tether/core support?
- The provided package signals do not state supported Laravel or PHP versions, so check composer.json for illuminate/* and php constraints plus the CI matrix. Because there are zero dependents, you cannot inherit compatibility findings from other projects. Test against your current and next major Laravel version in a branch before committing.
- Is tether/core a replacement for Laravel's built-in helpers and container?
- It should be treated as a thin typed veneer over Laravel's existing container, package discovery, config publishing, Str and Arr helpers, Collections, and PSR-backed contracts, not as a replacement. Read src/ to confirm it does not re-implement or shadow first-party primitives. If it duplicates what Laravel already maintains for free, you are taking on maintenance tax for a wrapper.
- How do I publish the tether/core configuration file?
- Use Laravel's standard vendor:publish command against the package's service provider tag, then review the published file for namespaced keys. The config is described as publishable and override-friendly, but confirm the exact tag in the README or service provider before running it in a shared application. Keep your overrides namespaced to avoid collisions with other packages.
- What are the production risks of adopting tether/core?
- The main risks are bus factor, security disclosure, and dependency pinning. The package has 10 stars, zero dependents, and a single-maintainer profile, so there is little production testimony and no inherited bug surface. Also verify composer.json pins against illuminate/*, symfony/*, and PSR constraints, and watch for static state or global helpers that can cause test-isolation problems.
- How should I test an application that depends on tether/core?
- Adopt it behind an internal interface and write contract tests against the behavior your application actually needs, not the package's implementation details. Resolve any facades through the container rather than relying on static state, and run the package's own test suite and CI signal before trusting it. Budget one to two engineering days for verification, since no other dependents have validated it.
- Does tether/core really have zero dependencies?
- The package claims zero runtime dependencies, but that claim deserves verification against illuminate/*, symfony/*, and PSR pins in composer.json. A single stale constraint can block a Laravel or PHP upgrade across your whole application under deadline pressure. Treat the zero-dependency claim as a hypothesis to test, not a guarantee.
- What alternatives exist to tether/core for Laravel package scaffolding?
- Laravel's first-party service container, package discovery, config publishing, Str and Arr helpers, Collections, and PSR contracts already cover most foundational needs. You can also use established package-skeleton tooling or write a small internal base package tailored to your conventions. Tether Core mainly pays off if you are adopting the sibling tether/* packages and want shared ecosystem conventions.
- Is tether/core actively maintained and safe to rely on long term?
- The available signals show 10 stars, zero dependents, and a low composite score, which does not demonstrate a release cadence or fork community. Check commit and release activity over the last twelve months, issue responsiveness, and CI status on the default branch before relying on it. If you adopt it, wrap it behind an internal interface so an abandonment in twelve months means rewriting a few call sites rather than the application.
Weaver
How can I help you explore Laravel packages today?