Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Contacts Laravel Package

inmanturbo/contacts

A Laravel package for managing contacts in your application. Store and organize contact records through an Eloquent-friendly API, making it easier to add address book or CRM-style features without building the data layer from scratch.

View on GitHub
Deep Wiki
Context7

At a glance

Frequently asked questions about Contacts
What is inmanturbo/contacts used for in Laravel?
inmanturbo/contacts is a Laravel package for managing contact records in your application. It provides an Eloquent-friendly API so you can add address book or CRM-style features without building the data layer from scratch. It is aimed at developers who want contact storage and organization to feel like normal Laravel models.
How do I install inmanturbo/contacts?
Install it with Composer using composer require inmanturbo/contacts. After installation, check the repository README for any required service provider registration, migration publishing, or configuration steps. Because package setup details can change between releases, follow the README for your installed version.
Which Laravel versions does inmanturbo/contacts support?
The supported Laravel versions are defined in the package's composer.json and README. Check those files before installing to confirm compatibility with your application's Laravel and PHP versions. If you are on an older or newer Laravel release, verify open issues or releases for guidance.
How does the Eloquent-friendly API work?
The package is designed around Eloquent, so contact records are managed through Laravel-style models rather than a separate query layer. You can use familiar Eloquent operations for creating, reading, updating, and deleting contacts, subject to the models and traits the package exposes. Refer to the README for the exact model class names and available relationships.
Does inmanturbo/contacts include database migrations?
A package that stores contact records typically needs database tables, and Laravel packages usually provide publishable migrations. Check the README for the exact migration publishing command and whether configuration is required. Run your normal Laravel migrations after publishing any package migrations.
Can I use inmanturbo/contacts to build a CRM or address book?
Yes, the package is described as a way to add address book or CRM-style contact management without building the data layer yourself. It is a good fit when you need contact records organized through Eloquent in a Laravel application. You would still build your own CRM workflows, UI, and business rules on top of the package.
How do I test inmanturbo/contacts in my Laravel app?
Use Laravel's normal testing tools, such as RefreshDatabase or DatabaseTransactions, so package tables are migrated for each test run. If the package provides factories or model factories, use them to create contact records in tests. Check the README for any package-specific testing notes or required setup.
Is inmanturbo/contacts suitable for production?
That depends on the package's current release quality, maintenance activity, and how well it fits your requirements. Review the repository's recent commits, releases, open issues, and test coverage before using it in production. Also confirm that its database schema and Eloquent behavior meet your data integrity needs.
What are alternatives to inmanturbo/contacts?
Alternatives include building your own Contact model and migrations with plain Eloquent, using a broader Laravel CRM or address book package, or integrating an external CRM API. The best choice depends on whether you need just contact storage or full CRM workflows. inmanturbo/contacts is focused on the Eloquent-friendly contact data layer.
How do I customize contact fields or extend the package?
Customization usually involves publishing and modifying migrations, extending the package's Eloquent models, or adding your own relationships and accessors. Check the README for supported extension points before changing vendor code. Keep customizations in your application code or published files so they survive Composer updates.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo
bernskioldmedia/laravel-harvest
bernskiold/laravel-data-scrubber
bernskiold/laravel-currency-converter
bernskiold/laravel-campaign-monitor
bernskioldmedia/laravel-autotranslate
siberfx/telegram-bot
roy-sandip/laravel-view-extended
gregsphotography/site-builder-core
roy-sandip/laravel-view
anodyne/blade-fluentui-icons
webx-ui/module-catalog-collections