alt-three/uuid
Alt Three UUID is a lightweight Laravel integration for generating UUIDs, giving applications a simple way to create unique identifiers through the framework’s service container. It helps add reliable UUID support to models, services, and other PHP code with minimal setup.
Architecture fit: The package is a narrow utility for converting UUIDs to integers, not a platform or domain component. It fits only as an internal helper in a legacy Laravel application that already requires integer-style UUID keys. Because UUIDs are 128-bit and native PHP integers are commonly 64-bit, the architecture must confirm whether the package returns a true integer, an arbitrary-precision decimal string, or a truncated value. For new systems, prefer native binary UUID storage, ramsey/uuid, or symfony/uid unless a documented legacy constraint requires this converter.
Integration feasibility: The code surface is likely small and MIT-licensed, so a fork or vendored copy is technically feasible. Direct Composer adoption is questionable: the last release was 2018, the repository is archived, and Laravel/PHP compatibility is likely limited to older stacks. Modern Laravel package discovery may work, but dependency constraints and stale service providers are likely friction points.
Technical risk: High for new adoption. The package has 12 stars, zero dependents, no active maintenance, and an archived repository. Key risks include overflow or truncation, collision exposure if all 128 bits are not preserved, inconsistent handling of malformed UUIDs, missing GMP/BCMath extensions, stale Laravel integration, and unclear database column expectations. It is acceptable only as a pinned legacy dependency behind an internal adapter, with tests proving round-trip integrity.
Key questions: Does the conversion preserve all 128 bits and round-trip reliably? Does it use native integers, strings, GMP, or BCMath? What PHP and Laravel versions are supported? What database type is expected: BIGINT, DECIMAL(39,0), binary, or string? Is the converter used for persistence, indexing, or display? Are there collision, boundary, and malformed-input tests? Can it be replaced by a maintained UUID library? Who owns patching and vulnerability response?
Stack fit: If the application is Laravel 5.x/PHP 7.x and already depends on this package, isolate it behind an application-owned adapter such as UuidConverterInterface. Do not let package classes leak into domain code. For Laravel 9+/PHP 8.x, do not adopt it directly; use maintained UUID tooling or native database UUID handling.
Migration path: For existing usage, inventory all call sites and database columns, add characterization tests for round-trip conversion, boundary values, invalid UUIDs, and duplicate keys, then fork the package into an internal namespace if necessary. Replace facade/provider usage with the adapter. Migrate storage only with dual-write or backfill validation. For new usage, reject the dependency and implement a small, tested converter only if the integer requirement is proven.
Compatibility: Verify Composer constraints for illuminate/support, PHP version, auto-discovery, and provider aliases. The archived package likely conflicts with modern Laravel and PHP releases. Confirm GMP/BCMath availability across environments and avoid implicit database casts for large numeric values. Test MySQL/PostgreSQL/SQLite behavior separately if storage is involved.
Sequencing: Confirm the business need for integer UUIDs; run a proof of concept on the target PHP/Laravel version; verify 128-bit round-trip and database types; choose fork versus replacement; wrap the chosen implementation in an adapter with tests; migrate or backfill in stages; remove the package once replacement is validated.
Maintenance: Ongoing code churn is low because the utility is small, but upstream maintenance is absent. The team must pin, fork, patch, and track PHP/Laravel compatibility internally. Budget a small but non-zero maintenance owner.
Support: There is no vendor or active community support, zero dependents, and limited documentation. MIT licensing grants legal permission to fork but does not provide operational support. Incident response and security review fall entirely to the internal team.
Scaling: Conversion CPU cost is negligible; database and index design dominate. Integer or decimal UUID storage may be larger or slower than BINARY(16) and can complicate indexing, replication, and cross-service interoperability. Validate query plans and cardinality before using converted UUIDs as primary keys.
Failure modes: Watch for overflow or truncation, collisions, invalid UUID exceptions, missing PHP extensions, stale Laravel service providers, Composer dependency conflicts, inconsistent endianness or UUID-version handling, and rollback issues during migration. Add monitoring for conversion errors and duplicate-key spikes.
Ramp-up: The code surface is small, but legacy Laravel patterns and undocumented numeric semantics increase ramp-up. New engineers should rely on adapter tests and runbooks rather than package-specific knowledge. Treat this as a legacy utility, not a strategic dependency.
How can I help you explore Laravel packages today?