Boolean Field Type Laravel Package

Product Decisions This Supports

• Build vs. buy for admin UI primitives. A boolean field type is a commodity UI primitive (a switch/toggle). This package lets you buy (adopt) that primitive for the Streams Platform rather than build it, which is the right call only when a native or maintained option doesn't exist.
• Ecosystem fit for CMS/data-modeling features. Relevant only if your roadmap includes Streams Platform / PyroCMS-based content modeling. It supports decisions like "which field types do we standardize on" and "how do we expose configurable admin controls to non-technical editors."
• Feature-scoping of toggle-style settings. If any product surface requires per-record on/off flags (feature toggles, publish/visible states, opt-ins), this package informs how those are represented and rendered in the data layer.
• Low-stakes adoption/experimentation. At MIT, ~2 stars, and 0 dependents, the "cost of trying" is negligible. It's a low-blast-radius dependency—useful for validating Streams-based prototypes without a procurement or security review cycle.
• Roadmap negative-space signal. The extremely low adoption (2 stars, 0 dependents) is itself a data point: don't build a strategy around this package or its ecosystem; treat it as a tactical utility.

When to Consider This Package

Adopt when:

• You are already committed to the Anomaly/Streams Platform or PyroCMS and need a checkbox/toggle field type in your content model.
• You want a fast, MIT-licensed, drop-in field type rather than authoring one yourself.
• The toggle is a non-critical admin convenience, not a core product mechanism requiring SLA, security guarantees, or active maintenance.

Look elsewhere (or build) when:

• You are not on the Streams Platform. This is not a general-purpose Laravel package—it's an ecosystem-specific addon and gives you nothing outside it.
• You need maintenance guarantees, support, or a growing community. With 2 stars and 0 dependents, there is effectively no community and no reliable maintenance signal—assess abandonment risk explicitly.
• The behavior is trivial to reproduce. A boolean field type is small enough that in-house implementation or a more mainstream package (e.g., a general admin/filament/livewire field library) may be a better long-term bet.
• You require security/compliance vetting of dependencies; an unmaintained single-purpose addon adds audit overhead disproportionate to its value.

How to Pitch It (Stakeholders)

Executive summary: This is a small, free (MIT-licensed), open-source addon that provides a simple on/off switch field for the Streams Platform (the framework behind PyroCMS). It is a tactical, low-cost component—not a strategic dependency. It saves a few hours of UI work if and only if we are already building on that platform. Its negligible adoption (2 stars, zero dependent projects) means we should treat it as "use, don't rely on"—no support contract, no vendor, minimal community. Recommendation: appropriate for prototypes or internal admin tooling inside a Streams-based project; not a reason to choose the platform, and we should have a fallback (build it ourselves, ~hours of work) if it goes stale. Risk: low (MIT, tiny surface). Value: modest and conditional.