PHPackages yezzmedia/laravel-ops - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Admin Panels](/categories/admin) 4. / 5. yezzmedia/laravel-ops ActiveLibrary[Admin Panels](/categories/admin) yezzmedia/laravel-ops ===================== Shared operations panel package for the Yezz Media Laravel website platform. 0.1.1(2mo ago)020↓90%2MITPHPPHP ^8.4CI passing Since Apr 12Pushed 1mo agoCompare [ Source](https://github.com/yezzmedia/laravel-ops)[ Packagist](https://packagist.org/packages/yezzmedia/laravel-ops)[ RSS](/packages/yezzmedia-laravel-ops/feed)WikiDiscussions main Synced 3w ago READMEChangelog (10)Dependencies (22)Versions (14)Used By (2) Laravel Ops =========== [](#laravel-ops) `yezzmedia/laravel-ops` is the shared operations panel package for the Yezz Media Laravel platform. It provides a Filament-based `/ops` panel with package, feature, diagnostics, audit, and access-facing operational surfaces on top of the normalized runtime exposed by foundation and, when installed, `yezzmedia/laravel-access`. Version ------- [](#version) Current release: `0.1.0` Requirements ------------ [](#requirements) - PHP `^8.4` - Laravel `^13.0` components - `filament/filament ^5.0` - `spatie/laravel-package-tools ^1.93` - `yezzmedia/laravel-foundation ^0.1` Optional: - `yezzmedia/laravel-access ^0.1` for the preferred ops authorization and access-management workflows - `spatie/laravel-activitylog` for audit-facing surfaces - `spatie/laravel-health` for richer diagnostics posture - `yezzmedia/laravel-ops-analytics ^0.1` for analytics posture, tracker, and consent-aware surfaces inside the shared ops panel - `yezzmedia/laravel-ops-backups ^0.1` for backup posture and restore-readiness surfaces inside the shared ops panel - `yezzmedia/laravel-ops-infrastructure ^0.1` for infrastructure posture inside the shared ops panel - `yezzmedia/laravel-ops-sites ^0.1` for site inventory and assignment posture inside the shared ops panel - `yezzmedia/laravel-ops-security ^0.1` for security posture and governance surfaces inside the shared ops panel - `yezzmedia/laravel-ops-settings` for operator-managed settings UI inside the shared ops panel Installation ------------ [](#installation) Install the package in the consuming Laravel application: ``` composer require yezzmedia/laravel-ops ``` The service providers are auto-discovered: - `YezzMedia\Ops\OpsServiceProvider` - `YezzMedia\Ops\OpsPanelProvider` Configuration ------------- [](#configuration) Publish the package config when you need to override panel defaults: ``` php artisan vendor:publish --provider="YezzMedia\Ops\OpsServiceProvider" --tag="config" ``` Default configuration: ``` return [ 'panel' => [ 'id' => 'ops', 'path' => 'ops', 'guard' => null, ], ]; ``` What The Package Provides ------------------------- [](#what-the-package-provides) ### Shared ops panel shell [](#shared-ops-panel-shell) `OpsPanelProvider` defines a dedicated Filament panel mounted at `/ops`. - uses the configured or resolved host auth guard - applies a dedicated ops authorization middleware boundary - registers the stable V1 ops pages and widgets - conditionally loads companion plugins when the corresponding packages are installed: - `YezzMedia\OpsAnalytics\Filament\OpsAnalyticsFilamentPlugin` - `YezzMedia\OpsBackups\Filament\OpsBackupsFilamentPlugin` - `YezzMedia\OpsInfrastructure\Filament\OpsInfrastructurePlugin` - `YezzMedia\OpsSites\Filament\OpsSitesFilamentPlugin` - `YezzMedia\OpsSecurity\Filament\OpsSecurityFilamentPlugin` - `YezzMedia\OpsSettings\Filament\OpsSettingsPlugin` ### Stable ops pages [](#stable-ops-pages) The package currently provides these operator-facing pages: - `OpsDashboard` - `PackagesPage` - `FeaturesPage` - `SystemHealthPage` - `AuditTrailPage` - `PermissionsPage` - `AccessManagementPage` The panel also registers detail pages that support drill-down workflows without adding extra top-level navigation entries: - `PackageDetailsPage` - `DoctorCheckDetailsPage` - `RoleDetailsPage` - `PermissionDetailsPage` - `AuditEntryDetailsPage` These surface the following routes: - `/ops` - `/ops/packages` - `/ops/features` - `/ops/diagnostics` - `/ops/audit` - `/ops/access/permissions` - `/ops/access/manage` ### Widgets and summaries [](#widgets-and-summaries) The dashboard currently includes: - `InstalledPackagesWidget` - `FailingChecksWidget` - `RecentActivityWidget` These build on the package summary, diagnostics summary, and recent activity resolver layers instead of duplicating query or registry logic in widgets. ### Authorization model [](#authorization-model) Ops declares a stable permission surface through foundation: - `ops.panel.access` - `ops.dashboard.view` - `ops.packages.view` - `ops.features.view` - `ops.diagnostics.view` - `ops.runtime.view` - `ops.audit.view` - `ops.access.view` - `ops.access.manage` When `yezzmedia/laravel-access` is not installed, ops falls back to reduced mode and uses the host-owned `viewOpsPanel` / `canAccessPanel()` boundary. When access is installed, the ops panel enforces the declared access permissions and unlocks the access-facing surfaces. ### Diagnostics and runtime posture [](#diagnostics-and-runtime-posture) `SystemHealthPage` and the diagnostics widget stack build on: - `RunSystemDiagnosticsAction` - `OpsDiagnosticsSummaryResolver` - `OpsDiagnosticsCacheManager` - `OpsRuntimePostureResolver` This keeps diagnostics collection and runtime posture aggregation in dedicated support classes instead of inside the page layer. ### Audit and access bridges [](#audit-and-access-bridges) `AuditTrailPage` uses the recent-activity resolver stack and degrades cleanly when no supported audit backend exists. `PermissionsPage` and `AccessManagementPage` use `OpsAccessBridge` to read from access-owned services rather than re-implementing permission-store or role-management logic inside ops. Those access-facing surfaces can: - inspect permission-store readiness - synchronize declared permissions - synchronize hinted roles - assign persisted roles to a user - remove persisted roles from a user The actual write operations remain delegated to access-owned runtime services. Foundation integration ---------------------- [](#foundation-integration) Ops registers itself with foundation through `OpsPlatformPackage`. That package descriptor currently provides: - package metadata for `yezzmedia/laravel-ops` - the stable ops permission declarations - an explicit ops-module surface, currently empty for V1 - security-governance declarations for the ops authentication entry point: - request `ops.request.auth.login-throttle` - requirement `ops.auth.login-throttle` These declarations are intentionally observe-only. Ops declares the required operator login-throttle posture, while verification stays in `yezzmedia/laravel-ops-security` and concrete runtime enforcement stays in the host auth and middleware layer. Development ----------- [](#development) Available package scripts: ``` composer test composer analyse composer format ``` License ------- [](#license) MIT ### Health Score 40 — FairBetter than 86% of packages Maintenance88 Actively maintained with recent releases Popularity6 Limited adoption so far Community10 Small or concentrated contributor base Maturity49 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~2 days Total 10 Last Release 75d ago PHP version history (2 changes)v0.1.0PHP ^8.2 0.1.0PHP ^8.4 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/107888802?v=4)[Yezz-Media](/maintainers/yezzmedia)[@yezzmedia](https://github.com/yezzmedia) --- Top Contributors [![yezzmedia](https://avatars.githubusercontent.com/u/107888802?v=4)](https://github.com/yezzmedia "yezzmedia (20 commits)") ### Code Quality TestsPest Static AnalysisPHPStan Code StyleLaravel Pint ### Embed Badge ![Health badge](/badges/yezzmedia-laravel-ops/health.svg) ``` [![Health](https://phpackages.com/badges/yezzmedia-laravel-ops/health.svg)](https://phpackages.com/packages/yezzmedia-laravel-ops) ``` ### Alternatives [mradder/filament-logger Audit logging, activity tracking, exports, alerts, and dashboards for Filament admin panels. 2310.5k](/packages/mradder-filament-logger)[rawilk/profile-filament-plugin Profile & MFA starter kit for filament. 3913.7k](/packages/rawilk-profile-filament-plugin)[nasirkhan/laravel-starter A CMS like modular Laravel starter project. 1.4k2.7k](/packages/nasirkhan-laravel-starter)[fleetbase/core-api Core Framework and Resources for Fleetbase API 1232.2k16](/packages/fleetbase-core-api)[api-platform/laravel API Platform support for Laravel 59156.3k11](/packages/api-platform-laravel)[a2insights/filament-saas Filament Saas for A2Insights 171.5k](/packages/a2insights-filament-saas) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)