Filament Lockbox Laravel Package

Product Decisions This Supports

• Feature scoping for admin-facing encrypted data: DecryptedTextDisplay supports decisions around whether to expose decrypted Lockbox values in Filament admin/support screens, with defined behavior for missing input, missing HasLockbox models, missing HasLockboxKeys users, and empty values.
• Build vs. buy for Filament integrations: If the product already uses Filament and a Lockbox-style encrypted-field pattern, this package can reduce custom UI work for decrypted display and model/user context checks.
• Custom auth/user-model roadmap: The filament-lockbox.user_model config override is a meaningful adoption enabler for applications with custom user models, multi-guard setups, or non-default auth architecture.
• Testability and integration confidence: New factories, test-user variants, and integration coverage lower the cost of validating the package in a consuming Laravel app, supporting a time-boxed pilot rather than a bespoke spike.
• Maturity gating: This is still 1.0.0-alpha.2. Product decisions should treat it as suitable for internal tooling, prototypes, or controlled pilots—not as a committed dependency for regulated or business-critical production workflows without a stability plan.

When to Consider This Package

Consider it when:

• The application is Laravel + Filament and needs a standardized way to display decrypted Lockbox values in admin or support interfaces.
• The team already has, or plans to adopt, HasLockbox / HasLockboxKeys model contracts and wants reusable context checks instead of custom glue code.
• A custom user model is required and must be configurable via config/filament-lockbox.php.
• The team can accept alpha-level maturity and wants improved integration tests/factories to evaluate fit quickly.
• The product needs graceful UI fallbacks for missing decrypted values, missing input, or incompatible models/users.

Look elsewhere or defer when:

• The product requires a stable, production-critical dependency with long-term compatibility guarantees.
• The stack is not Laravel/Filament or does not use a Lockbox-style encrypted-field model.
• The product needs advanced key-management, rotation, audit, or compliance features that are not evidenced in this release.
• The team cannot absorb alpha-stage API changes or maintain a fork/patch path.
• The integration requires guarantees around authorization, access logging, or regulatory controls beyond what the package documents.

How to Pitch It (Stakeholders)

For executives: This is an early-stage Laravel/Filament package that can reduce custom development for safely displaying decrypted Lockbox data in internal admin screens. The latest alpha improves test coverage, adds reusable test factories, and fixes custom user-model configuration—making it easier to evaluate. It is not yet a production-critical dependency; position it as a controlled pilot until it reaches a stable release.

For engineering: The release strengthens confidence in DecryptedTextDisplay behavior and removes hardcoding around filament-lockbox.user_model, which matters for custom auth models. New factories and shared traits reduce test setup and duplication. Static-analysis fixes are housekeeping, not architectural changes. Adopt only if the team is comfortable with alpha maturity and can validate the Filament/Lockbox integration in-app.