- What does leads/core include for Laravel lead management?
- The package provides a foundational domain layer for lead management, including a Lead model, migrations for persistent records, status and source tracking for qualification workflows, and an assignment-ready structure for ownership and follow-ups. It is designed as a convention-driven, extensible base that fits into existing Laravel applications rather than a full CRM. The repository README should be checked for the exact public surface, because domain services, routes, views, and policies are not all confirmed by the package description alone.
- How do I install leads/core in a Laravel application?
- Install it through Composer as leads/core and let Laravel package discovery register any service provider if the package supports it. Then check whether migrations or configuration files need to be published before running migrations, and review the package defaults against your application schema. The install itself is cheap; the real setup cost is verifying how its models and casts interact with your existing database and auth setup.
- Which Laravel versions does leads/core support?
- The provided package context does not state a Laravel version range, so check the require constraints in the package composer.json before adding it to a project. Confirm the PHP version and any Illuminate dependencies as well, especially if you are on an older Laravel release. Do not assume compatibility from the Composer install succeeding alone; run the package tests or a small integration spike on your target version.
- Is leads/core safe to use in production?
- Treat it as unvetted for production until you complete a dependency and code review. It has zero stars and zero known dependents, no public issue history, and a single maintainer, so there is little external validation of failure modes or supply-chain safety. A timeboxed spike plus a Composer audit and license check is advisable before writing a version constraint into a production application.
- What is DateCaster in leads/core and why does it matter?
- DateCaster is an Eloquent attribute-casting behavior introduced in release 1.2.1, and it indicates the package sits inside the persistence layer rather than being a pure domain library. A patch release that widens accepted datetime input formats can be backwards-compatible under semver while still changing the shape or precision of data written before and after the upgrade. Determine whether the caster is opt-in per attribute, applied through a trait, or bound globally; global binding is a significant adoption risk.
- Does leads/core include database migrations and tables?
- The package overview lists migrations for persistent lead records, so it likely creates or expects database tables that must coexist with your application schema. What is not confirmed is whether those migrations are publishable, how table names are chosen, and whether they can be customized cleanly. Review the migration files and table ownership before running them against an existing production database.
- Does leads/core assume a specific auth, tenancy, or queue setup?
- The package is described as assignment-ready for ownership and follow-ups, but the context does not confirm which user model, tenancy strategy, or queue driver it expects. Those assumptions matter because a lead package often touches ownership columns, authorization policies, and background follow-up jobs. Inspect the migrations, contracts, and service bindings to see whether it couples to a specific auth guard or tenant resolver before integrating it into a multi-tenant application.
- How do I extend leads/core with custom lead workflows?
- It is positioned as an extensible, convention-driven foundation with reusable models, contracts, and services, so custom statuses, sources, and assignment rules should be layered on top rather than patched into vendor code. Prefer depending on its public contracts where they exist and keep your own business logic in application-level services. Confirm the public API is an interface you can rely on, not an implementation detail such as a globally bound caster or base model.
- Is leads/core actively maintained?
- There is evidence of process: a 1.2.0 to 1.2.1 progression, a release-drafter changelog, a linked pull request, and a semver patch bump. However, it remains a single-maintainer package with no external production validation, so bus factor is an unhedged staffing dependency. The future-dated 2026-08-25 release tag should be mapped to a commit before you pin any version constraint.
- What should I check before adopting leads/core or choosing an alternative?
- Start with a short spike that inspects the shipped files, confirms whether DateCaster is global or opt-in, tests datetime input normalization, and checks migration conflicts against your schema. Verify the license for commercial use and forking, run Composer audit for transitive dependency risk, and confirm the public surface you would depend on. If those checks fail, a custom Laravel lead model or a more established CRM package may be a safer alternative for production.