Download the PHP package maatify/php-slug without Composer

Publication State

v1.0.0-rc.2 is the current Published Release Candidate available through Packagist. It remains Pre-Stable, does not create a Stable support line, and there is no Published Stable release. Publication does not imply Stable readiness.

The current public contract is owned by SLUG_PACKAGE_REFERENCE.md. Execution evidence is maintained in GitHub PR and CI history rather than duplicated in this consumer-facing README.

Package Summary

maatify/php-slug is a standalone PHP library for slug generation, canonicalization, scoped ownership, lifecycle management, aliases, history, resolution, and package-owned PDO MySQL persistence.

Key Features

• Slug Generation & Canonicalization: Consistent generation and canonicalization through versioned built-in profiles.
• Ownership & Lifecycle: Exact claiming, generated allocation, release, scope transition, atomic transfer, and adoption.
• Aliases & History: Active and retired aliases with immutable lifecycle history.
• Persistence & Concurrency: PDO MySQL-compatible persistence with transactions, CAS, and concurrency guarantees.
• Resolution & Management: Resolution, availability, Scope discovery, Scope operational summaries, operational History windows, and management reads with shared pagination.
• Public Extension: Versioned custom Slug profiles through the public registry path, plus Host-owned reserved-slug policy injection.

Requirements

Built-in profiles require the normalization and transliteration capabilities provided by ext-intl; the package verifies those capabilities at runtime. No exact ICU or Unicode version is required from the consumer.

Installation

Install the published Release Candidate with:

Quick Usage

The stateless path does not require a database or Host framework:

For the persisted path, the Host injects a PDO connection, a ReservedSlugPolicyInterface, and a ClockInterface into SlugEngineFactory::create(...). See docs/guides/USAGE_GUIDE.md for the complete workflow.

Public Runtime API

The public Runtime provides actual paths for:

• canonicalization through SlugTextServiceInterface, generateFromSource, canonicalizeClaim, and canonicalizeLookup;
• lifecycle ownership through SlugEngine and SlugLifecycleServiceInterface, including assignExact;
• consumer reads through checkAvailability, getCurrent, and resolve; and
• management reads through SlugManagementQueryInterface, including searchScopes, getScopeOperationalSummary, and searchHistory in the published RC2 Runtime.

This overview does not replace the complete inventory and contracts in SLUG_PACKAGE_REFERENCE.md.

Examples

• examples/canonicalization.php: a stateless generation and canonicalization example.
• examples/custom-profile.php: a stateless custom profile registration and usage example.
• examples/persisted-lifecycle.php: a persisted MySQL lifecycle example using the canonical Compose flow.

The canonicalization and custom-profile examples run without Docker. The persisted example requires the Integration environment provided by tools/ci/run-gate.sh.

Documentation

• docs/guides/USAGE_GUIDE.md — consumer usage and integration.
• examples/ — runnable consumer examples.
• SLUG_PACKAGE_REFERENCE.md — the current public contract and Public API reference.
• CHANGELOG.md — change history and publication state.
• SECURITY.md — security policy and reporting route.
• CONTRIBUTING.md — development setup and verification commands.
• README_AR.md — non-canonical Arabic translation of this README.

Transactions and Concurrency

On the persisted path, the package owns the transaction when the Host has no outer transaction and uses a savepoint when participating in an outer transaction where the capability is supported. Exact claims rely on the unique Registry constraint as the final race authority and use lifecycle mutation CAS and idempotency according to the contract. See SLUG_PACKAGE_REFERENCE.md for the normative details.

Security and Trust Boundaries

The Host owns the connection, PDO configuration, entity existence, routing, HTTP, SEO, and authorization. The package does not create hidden connections or use Host foreign keys or joins. For vulnerability reports, see Security Policy; do not disclose private vulnerability details through GitHub Issues.

Exceptions and Error Propagation

Package-defined semantic and domain failures use the SlugExceptionInterface / SlugDomainExceptionInterface hierarchy described in the Package Reference. External infrastructure Throwable instances, including PDO failures outside the documented semantic conversions, may propagate unchanged according to the current contract.

Quality Status

The package is maintained behind the repository's configured CI and quality gates. Current execution evidence is maintained in GitHub PR and CI history. The Published Release Candidate remains Pre-Stable and does not claim Stable readiness.

Development and Testing

For repository setup, tests, and example gates, see CONTRIBUTING.md. The persisted example requires the canonical Compose lifecycle and disposable MySQL; do not use an external MySQL instance.

License

Licensed under the MIT License.

👤 Author

Engineered by Mohamed Abdulalim (@megyptm)
Backend Lead & Technical Architect
https://www.maatify.dev