README

Quickstart

Install individual capabilities where possible. The metapackage composes 21 members and has no runtime services; Billing and Payments are separate opt-in installs. Follow the standalone getting-started guide, then use nvl:install <loaded-package> and each package's native bindings/configuration. Installation does not adopt host Auth/Tenancy or enable ingress.

Testing your app

Use each installed package's focused contracts, native container substitution and shipped fixtures. The metapackage has no model factory, fake or event schema. Include Core's optional consumer-audit.neon in host PHPStan; suite workbench tools are maintenance-only. See each member's README and events catalog for runtime contracts. The published 5.x family is verified through the local Dagger release gate on PHP 8.4/Laravel 13, including owning suites, MySQL/PostgreSQL persistence contracts and sealed Tenancy consumers. Fresh public Composer installation, discovery and configuration/route caching are verified. PHP 8.5, Laravel 12, MariaDB and the full independent archive matrix require separate evidence. See the verification and release policy.

nvl/laravel-suite 5.x is a Composer metapackage that installs the 21 independently published NVL Laravel packages. It contains no application code or service provider. Each package has its own repository, release tags, configuration, and documentation.

Install

The verified release configuration is PHP 8.4 with Laravel 13. Composer also admits PHP 8.5 and Laravel 12; those compatibility legs require separate evidence. Install the published stable family:

composer require nvl/laravel-suite:^5.0

Follow the installation and publishing guide before migrating an existing application. It lists every package's configuration, migration, skill, translation, view, and adoption publish tag.

For a smaller application, install only the packages you need, for example:

composer require nvl/core:^5.0 nvl/filterable:^5.0

Composer resolves each package's declared dependencies. Core contains the shared Support and Data namespaces. Filterable remains an independent package. Tenancy is required by packages that use its contracts, but tenant behavior starts disabled. The full suite installs Auth with HTTP ingress and host adoption disabled. Principal, password broker and Spatie storage adoption are independent explicit choices; review their configured host targets before enabling them. Consult each package README before enabling routes, migrations, or integrations.

Package-owned agent skills can be published from the relevant provider with its documented vendor:publish tag. Use canonical nvl-<package>-skills tags documented by each provider; Core ships both Support and Data guidance. Installing the suite does not publish those files automatically.

Packages

Foundation and localization: Core, Filterable, Primitives, Tenancy, Translatable, Translations.

Application capabilities: Activity, Auth, Comments, Content, CSV, Forms, Mail Notifications, Media, Metafields, Pages, SEO, Settings, Tasks, Taxonomy, Templates.

How the repositories are maintained

The public package repositories are release mirrors of a private source monorepo. Each package has its own Composer dependencies and version tags. A compatible patch to one package can be released without publishing every other package or a new suite version. The suite metapackage needs its own release when its dependency constraints or public documentation change.

Maintainers merge and test changes in the source monorepo, then publish the affected public mirror tags. Packagist indexes those tags; consumer applications need only the public repositories. Direct edits and pull requests in a mirror do not update source. Browse the organization profile for package descriptions and use each package's README for public documentation. Open an issue in the affected package repository, or a suite issue for installation and composition questions. Proposed patches can be attached to an issue; see Contributing.

Versions and support

The published 5.x suite requires ^5.0 for all 21 members. Billing and Payments are separate ^5.0 installs. All family majors move together; package minors and patches stay independent. Stable 5.0.0 tags for all 23 code packages and the metapackage are available on Packagist. Fresh public installation of the suite plus Billing and Payments passed, including package discovery and configuration/route caches. Historical suite 4.x selected Tasks 3.x and Activity 2.3; suite 3.x remained on Tasks 2.x. Before upgrading an existing application from suite 3.x, read the Tasks 3 upgrade guide: apply the new Tasks migrations using your existing migration ownership mode, review removed Content and Metafields integrations, and restart workers. The historical 2.x suite was a bundled library; upgrading from it also changes the Composer dependency graph. See each package README for activation and migration guidance. Report vulnerabilities through the affected package's private vulnerability reporting form, or use the suite's private form if the affected package is uncertain.

Released under the MIT License.

Canonical configuration ownership

This provider-free metapackage ships no config file or environment inputs of its own. Configure each installed capability through its shipped canonical files; Core ships both nvl-core.php and nvl-data.php.

License

MIT. See LICENSE.

Verification and releases

Maintainer CI runs locally through a pinned Dagger engine on Docker. The release gate checks standards, maximum PHPStan analysis, root and owning package suites, MySQL 8.4/PostgreSQL 17 persistence contracts and sealed Tenancy consumers with Redis and S3-compatible storage. Passing evidence is bound to the exact clean source commit. The 5.0.0 gate passed at 4950de7e818ed1578b5753afe045d2c70637f32c on 2026-10-08.

GitHub Actions is used only for explicitly requested package publishing. Pushes, pull requests and schedules start no hosted quality jobs; Dagger Cloud Checks are disabled. Each public repository is a release mirror of the private monorepo. Maintainers develop in source, verify locally, then publish an immutable package tag; Packagist indexes that tag. A compatible package patch can be released independently within family major 5.

Consumers use ordinary composer require nvl/<package>:^5.0 without private repository access. Commit the application lockfile, review installed package defaults and upgrade guides, select migration ownership, bind host authorization, then run strict Doctor and the application's own tests before enabling features. Package verification covers the listed configurations; it does not certify an arbitrary host application or every declared compatibility leg.

nvl / laravel-suite

Package info

Security

Statistics