PHPackages yezzmedia/laravel-foundation - 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. [Framework](/categories/framework) 4. / 5. yezzmedia/laravel-foundation ActiveLibrary[Framework](/categories/framework) yezzmedia/laravel-foundation ============================ Foundation package for the Yezz Media Laravel website platform. 0.1.1(1mo ago)0207MITPHPPHP ^8.3 Since Mar 28Pushed 3w agoCompare [ Source](https://github.com/yezzmedia/laravel-foundation)[ Packagist](https://packagist.org/packages/yezzmedia/laravel-foundation)[ RSS](/packages/yezzmedia-laravel-foundation/feed)WikiDiscussions main Synced 1w ago READMEChangelog (2)Dependencies (9)Versions (4)Used By (7) Laravel Foundation ================== [](#laravel-foundation) `yezzmedia/laravel-foundation` is the shared platform core for Yezz Media package-based Laravel applications. It provides the stable runtime that downstream platform packages build on: package registration, feature and permission registries, install and doctor orchestration, cache and rate-limit key factories, platform console commands, and reusable Testbench support for consumer packages. Version ------- [](#version) Current release: `0.1.0` Requirements ------------ [](#requirements) - PHP `^8.3` - Laravel `^13.0` support and console components - `spatie/laravel-package-tools ^1.93` Installation ------------ [](#installation) Install the package in the consuming Laravel application: ``` composer require yezzmedia/laravel-foundation ``` The service provider is auto-discovered. Configuration ------------- [](#configuration) Publish the package config when you need to override defaults: ``` php artisan vendor:publish --provider="YezzMedia\Foundation\FoundationServiceProvider" --tag="config" ``` Default configuration: ``` return [ 'registry' => [ 'seal_after_boot' => true, ], 'rate_limits' => [ 'separator' => ':', ], 'cache' => [ 'prefix' => 'website', 'separator' => ':', ], ]; ``` What The Package Provides ------------------------- [](#what-the-package-provides) ### Foundation runtime bootstrapping [](#foundation-runtime-bootstrapping) `FoundationServiceProvider` registers the shared platform services that downstream packages consume. It binds: - `PackageRegistry` - `FeatureRegistry` - `PermissionRegistry` - `OpsModuleRegistry` - `SecurityRequestRegistry` - `SecurityRequirementRegistry` - `PackageManifestLoader` - `PlatformPackageRegistrar` - `InstallManager` - `DoctorManager` - `CacheKeyFactory` - `RateLimitKeyFactory` - `IntegrationManager` - `ResolvesSiteContext` After boot, foundation seals the registries by default so the normalized package state stays read-only during ordinary runtime flows. ### Package registration [](#package-registration) Downstream packages integrate with foundation by registering a descriptor that implements `PlatformPackage`. Foundation normalizes that descriptor through `PlatformPackageRegistrar` into the shared registries. Supported capability contracts include: - `RegistersFeatures` - `DefinesPermissions` - `DefinesAuditEvents` - `ProvidesDoctorChecks` - `ProvidesOpsModules` - `DefinesInstallSteps` - `DefinesRateLimiters` - `DefinesCacheProfiles` - `DefinesSecurityRequests` - `DefinesSecurityRequirements` Example registration pattern: ``` use Spatie\LaravelPackageTools\Package; use Spatie\LaravelPackageTools\PackageServiceProvider; use YezzMedia\Foundation\Support\PlatformPackageRegistrar; final class ExampleServiceProvider extends PackageServiceProvider { public function configurePackage(Package $package): void { $package->name('example-package'); } public function packageBooted(): void { app(PlatformPackageRegistrar::class)->register(new ExamplePlatformPackage); } } ``` ### Registries and normalized state [](#registries-and-normalized-state) Foundation provides central registries for the normalized platform surface: - packages - features - permissions - ops modules - security requests - security requirements These registries are what install, doctor, package listing, and feature listing work against. ### HTTP middleware declarations and bridge [](#http-middleware-declarations-and-bridge) Foundation also provides a shared declaration surface for package-owned HTTP middleware wiring. The relevant capability and runtime pieces are: - `DefinesHttpMiddleware` - `HttpMiddlewareDefinition` - `HttpMiddlewareRegistry` - `HttpMiddlewareResolver` - `FoundationHttpMiddlewareBridge` This lets downstream packages declare stable middleware definitions instead of patching the host bootstrap directly from package code. Supported declaration kinds include: - `alias` - `web_prepend` - `web_append` Foundation resolves those declarations deterministically and applies them through the bridge at host boot time. The foundation package itself currently ships: - `ConfigureHttpMiddlewareBridgeInstallStep` to patch the standard Laravel 13 middleware bootstrap block when the host explicitly requests installation work - `FoundationHttpMiddlewareBridgeConfiguredCheck` to verify that the host bootstrap actually applies the bridge during diagnostics Typical host flow: ``` php artisan website:install --only=yezzmedia/laravel-foundation php artisan website:doctor ``` This keeps package-owned middleware aliases and web-stack injections explicit, auditable, and consistent across consumer packages. ### Security governance declarations [](#security-governance-declarations) Foundation now provides the shared declaration surface that downstream packages use to describe security intent without taking over runtime enforcement. The new declaration contracts are: - `DefinesSecurityRequests` - `DefinesSecurityRequirements` The new DTOs are: - `SecurityRequestDefinition` - `SecurityRequirementDefinition` The new registries are: - `SecurityRequestRegistry` - `SecurityRequirementRegistry` `PlatformPackageRegistrar` validates and registers both declaration types. The current normalized vocabulary supports: - domains: `auth`, `identity`, `session`, `transport`, `runtime`, `secrets` - levels: `required`, `recommended`, `optional`, `disallowed` - enforcement modes: `observe_only`, `package_owned`, `centrally_enforced` Security request definitions also support payload-shape validation, preview-field allowlists, and masked-field declarations so downstream governance tooling can stay explicit about what may be shown to operators. Foundation's role remains declarative: - feature packages declare security requests and requirements - foundation validates and registers those declarations centrally - downstream packages such as `yezzmedia/laravel-ops-security` evaluate and verify runtime reality Foundation does not compute effective security policy and does not enforce authentication or settings behavior itself. ### Install and doctor workflows [](#install-and-doctor-workflows) `InstallManager` orchestrates declared install steps across registered platform packages. - runs package install steps in deterministic order - supports filtering with explicit package names - carries one explicit `InstallContext` through the run so steps can react to operator intent - supports explicit migration permission through `--migrate` - supports explicit published-resource refresh through `--refresh-publish` - supports explicit host bootstrap patching for the foundation HTTP middleware bridge - stops on the first blocking failure - reports executed, failed, and skipped steps through `InstallResult` Migration note for consumer packages: - custom install steps must now accept `InstallContext` in both `shouldRun()` and `handle()` - packages that still implement the older no-context install-step signatures must update those method signatures before adopting the current foundation runtime Foundation also registers itself into the package registry with priority `0`, so package inventory and downstream diagnostics always include the platform core. `DoctorManager` aggregates declared doctor checks across registered platform packages. - validates check metadata and result shape - supports normalized statuses: - `passed` - `warning` - `failed` - `skipped` - separates blocking failures from non-blocking output ### Console commands [](#console-commands) Foundation exposes these platform commands: ``` php artisan website:install php artisan website:install --only=yezzmedia/laravel-access php artisan website:install --migrate php artisan website:install --refresh-publish php artisan website:doctor php artisan website:packages php artisan website:features ``` - `website:install` runs declared install steps - `website:install --migrate` explicitly allows install steps to run required migrations - `website:install --refresh-publish` explicitly allows install steps to refresh already published resources - `website:doctor` reports declared doctor checks - `website:packages` lists registered platform packages - `website:features` lists registered platform features Foundation currently declares one install step and one doctor check of its own: - install step: `ConfigureHttpMiddlewareBridgeInstallStep` - doctor check: `FoundationHttpMiddlewareBridgeConfiguredCheck` ### Audit persistence install flow [](#audit-persistence-install-flow) Foundation now supports explicit audit persistence setup inside `website:install` instead of using a separate top-level command. Supported command shape: ``` php artisan website:install --configure-audit php artisan website:install --configure-audit --audit-package=all php artisan website:install --configure-audit --audit-package=yezzmedia/laravel-access ``` Behavior: - `--configure-audit` starts an explicit audit-persistence setup flow - `--audit-package=*` narrows the flow to selected installed packages - `all` enables audit setup for every installed audit-capable package - interactive package selection runs when `--configure-audit` is passed without `--audit-package` - `--configure-access-audit` remains available as a deprecated access-only alias - audit setup runs only package-owned audit install steps and does not execute ordinary install, migration, or seeding steps ### Key factories [](#key-factories) Foundation ships reusable key factories for downstream packages: - `CacheKeyFactory` - `RateLimitKeyFactory` These keep cross-package technical identifiers consistent. ### Events [](#events) Foundation emits platform lifecycle events such as: - `PackageRegistered` - `FeatureRegistered` - `PermissionDefined` - `OpsModuleDefined` - `WebsiteInstalled` - `DoctorChecksCompleted` ### Testing support [](#testing-support) Foundation exposes a reusable Testbench base and helper concerns for consumer package tests: - `YezzMedia\Foundation\Testing\FoundationTestCase` - `YezzMedia\Foundation\Testing\Concerns\InteractsWithPackageRegistry` - `YezzMedia\Foundation\Testing\Concerns\InteractsWithFeatureRegistry` - `YezzMedia\Foundation\Testing\Concerns\InteractsWithDoctorManager` - `YezzMedia\Foundation\Testing\Concerns\InteractsWithInstallManager` These helpers keep consumer package tests on the real foundation registration path while reducing repetitive setup. Consumer package usage ---------------------- [](#consumer-package-usage) Foundation is intended to be consumed by platform packages, not by feature code that wants to bypass package registration. Use it when building packages that need to: - declare stable permissions - register features - expose install steps or doctor checks - participate in shared platform ops workflows - test package registration through a real Testbench baseline Boost skills ------------ [](#boost-skills) The package ships package-native Boost skills for both sides of foundation work: - `resources/boost/skills/foundation-package-development/` - `resources/boost/skills/foundation-core-development/` These document the approved package-consumer and core-runtime workflows for the foundation architecture. Development ----------- [](#development) Available package scripts: ``` composer test composer analyse composer format ``` License ------- [](#license) MIT ### Health Score 39 — LowBetter than 84% of packages Maintenance92 Actively maintained with recent releases Popularity6 Limited adoption so far Community13 Small or concentrated contributor base Maturity41 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 ~14 days Total 2 Last Release 58d ago ### 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 (15 commits)") ### Code Quality TestsPest Static AnalysisPHPStan Code StyleLaravel Pint ### Embed Badge ![Health badge](/badges/yezzmedia-laravel-foundation/health.svg) ``` [![Health](https://phpackages.com/badges/yezzmedia-laravel-foundation/health.svg)](https://phpackages.com/packages/yezzmedia-laravel-foundation) ``` ### Alternatives [laravel/sail Docker files for running a basic Laravel application. 1.9k199.2M1.2k](/packages/laravel-sail)[spatie/laravel-responsecache Speed up a Laravel application by caching the entire response 2.8k8.7M64](/packages/spatie-laravel-responsecache)[laravel/ai The official AI SDK for Laravel. 9782.1M153](/packages/laravel-ai)[spatie/laravel-health Monitor the health of a Laravel application 88011.3M149](/packages/spatie-laravel-health)[laravel/mcp Rapidly build MCP servers for your Laravel applications. 76318.2M110](/packages/laravel-mcp)[laravel/jetstream Tailwind scaffolding for the Laravel framework. 4.1k21.1M148](/packages/laravel-jetstream) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)