Weave Code
Legal Entity Laravel Package
amethyst/legal-entity
A Laravel package for managing legal entities, offering structured models and migrations for companies, addresses, registrations, and related business data. A clean, extensible foundation for apps that need to store and organize organizational records.
At a glance
Frequently asked questions about Legal Entity
- Is amethyst/legal-entity a Laravel package?
- No. It is a framework-agnostic domain aggregate from the Amethyst ecosystem, not a Laravel component. There is no service provider, auto-discovery, published config, or Artisan tooling. In a Laravel app its realistic role is a typed DTO or domain model behind your own adapter.
- How do I install amethyst/legal-entity with Composer?
- Install it with composer require amethyst/legal-entity; it is MIT licensed and has no native extensions. Expect no Laravel package discovery, so wiring is manual. Run a sandbox install first and check resolution against your target PHP and Laravel versions before committing to the dependency.
- Does amethyst/legal-entity support Laravel 10 or Laravel 11?
- The package declares no Laravel version constraint matrix, and the Amethyst family has seen little activity for several years. Transitive dependencies may pin older PHP or PSR versions and trigger composer why-not conflicts on Laravel 10/11 and PHP 8.2+. Verify resolution in isolation before assuming compatibility.
- Can I use amethyst/legal-entity with Eloquent models?
- Not directly. It composes with amethyst/aggregate, amethyst/model, and amethyst/serializer rather than Eloquent, so it will not replace your models or migrations. Map explicitly between the aggregate and your Eloquent records, and keep Amethyst types out of controllers, jobs, and API resources.
- What legal entity data does the package model?
- It provides structured models for companies, addresses, registrations, and related business data such as legal name, registration identifiers, and entity type. The aggregate is generic, so jurisdiction-specific details like Companies House, Handelsregister, or EIN normalisation, beneficial ownership, and address formatting may not be covered. Do a schema gap analysis against your actual requirements.
- Is amethyst/legal-entity safe to use in production?
- There is no external evidence of production use: zero stars, zero dependents, and no documented quality score. The Amethyst family has low recent activity and effectively a single-maintainer bus factor, so security advisories and compatibility testing are unlikely. The codebase is small enough to audit and vendor, but only adopt it if you accept ownership.
- Does amethyst/legal-entity include migrations or config publishing?
- No. It ships no Laravel service provider, no publishable configuration, no migrations, and no validation layer. Persistence, schema design, and HTTP validation remain your responsibility. Treat it as a library of value objects rather than infrastructure.
- How should I integrate amethyst/legal-entity into a Laravel domain layer?
- Use an adapter-first approach: define your own LegalEntity interface and repository contract in application code, then implement them with this package behind a thin mapping class. Add fixture-based contract tests around the adapter so the dependency stays swappable. Start with one narrow production path, such as company ingestion from a single registry, before broadening.
- What are the alternatives to amethyst/legal-entity for Laravel?
- Most Laravel teams model legal entities with Eloquent models, casts, and custom value objects, sometimes using DTO packages such as spatie/laravel-data. If you already use the Amethyst ecosystem, this package composes naturally with amethyst/aggregate and amethyst/serializer. Otherwise compare its schema against your jurisdiction needs before adding an isolated dependency.
- How do I test amethyst/legal-entity in a Laravel project?
- There is no evidence of test coverage or CI on current PHP versions, so do not rely on the package's own tests. Write contract tests against your adapter using fixtures that represent your registry data and address shapes. Also run a Composer resolution spike in a clean sandbox to catch dependency conflicts early.
Weaver
How can I help you explore Laravel packages today?