Encrypted Field Type Laravel Package

Product Decisions This Supports

• Feature: encrypted custom fields. Enables sensitive values—PII, API keys, tokens, recovery codes, client secrets—to be stored as encrypted fields inside an Anomaly/Streams-based CMS instead of plaintext or a separate secrets store.
• Roadmap: “secure fields” or compliance-lite storage. Supports internal admin tools and content workflows that need field-level encryption at rest without building custom encryption plumbing.
• Build vs. buy: Buy/integrate only if the product is already committed to Anomaly/Streams. Otherwise, a small internal Laravel encrypted cast/accessor is likely lower-risk than adopting a 0-star, 0-dependent package.
• Prioritization signal: Recurring requests for secrets/PII in CMS entries justify a time-boxed spike. The low package score (0.24), zero stars, and zero dependents mean this is not a platform bet without security review.
• Risk decision: Treat as unproven and forkable MIT code. Require code review, tests, key-management design, and a contingency plan before production use.

When to Consider This Package

• You are already using Anomaly/Streams and need an encrypted field type for CMS entries.
• You need a quick POC for encrypted custom fields and can inspect, pin, and vendor/fork the package.
• The data is small-scope, internal, low-to-medium risk, and does not require searchable encryption, KMS/HSM integration, or formal compliance certification.
• You can own maintenance: security review, encrypt/decrypt tests, key rotation, migration handling, and upgrade path.
• Look elsewhere if you are not on Anomaly/Streams, need a general Laravel encryption framework, need vendor support or proven adoption, or require enterprise key management, audit trails, searchable encrypted fields, or compliance controls.

How to Pitch It (Stakeholders)

Executives: This is a small MIT-licensed add-on that could add encrypted fields to our Anomaly/Streams CMS and save build time for sensitive-data capture. However, it has no visible adoption—0 stars, 0 dependents—and is not a compliance control by itself. Recommend a time-boxed spike behind a feature flag, not a platform commitment.

Engineering: It is a field-type add-on, not a general Laravel encryption library. If adopted, vendor/fork it, add tests for encryption/decryption, key rotation, migrations, and failure modes, and document key management. Use it for internal low-to-medium-risk data until it has been security-reviewed and proven in production.