Product Decisions This Supports

Feature scoping and content visibility: Use an Eloquent-native exclusion mechanism to hide records from default queries without deleting them—useful for archived items, moderated content, draft/private records, or feature-flagged entities.
Build vs. buy: Avoid writing and maintaining custom global scopes for simple exclude/include behavior. Buy/adopt when the need is a straightforward boolean or timestamp-based exclusion pattern across models.
Roadmap sequencing: Low-effort enabler for features like “hide from catalog,” “exclude from feeds,” or “soft-archive” without introducing deletion workflows or data-loss risk.
Operational safety: Supports reversible visibility changes, reducing the need for hard deletes and helping preserve referential integrity.
Laravel 11 readiness: Release 4.1.0 adds Laravel 11.x compatibility, removing a framework-upgrade blocker for teams standardizing on Laravel 11.

When to Consider This Package

You need a simple, reusable exclusion pattern in Laravel/Eloquent—e.g., a model can be globally excluded from queries and explicitly included when needed.
Your team wants to avoid bespoke global scopes for common hide/archive behavior and prefers a small, focused package.
You are on a supported Laravel version; 4.1.0 explicitly adds Laravel 11 compatibility.
You want exclusion logic to remain query-layer concern, not domain-complex authorization or workflow logic.
Look elsewhere if you need complex authorization policies, audit trails, regulatory retention, multi-step moderation, hard-delete guarantees, or sophisticated state machines. This package is not a substitute for Laravel policies, soft deletes, or compliance-grade auditing.

Executive summary: A small Laravel package that gives teams a standard way to hide records from normal queries without deleting them. The 4.1.0 release adds Laravel 11 support, making it viable for teams upgrading their platform.
Engineering summary: Adopt for simple Eloquent exclusion needs to reduce custom scope code and maintenance. It is low-risk and Laravel-idiomatic, but should not be used for authorization, compliance retention, or complex moderation workflows. Validate fit against existing soft-delete and policy patterns before standardizing.