roots/bedrock
50.5
Adequate · 17 November 2026
213
lines of production code
PHP
primary language
5
measurements over time
What this system is
Features
Add local development environment with dev container
Developers can now run the project locally using VS Code Dev Containers. This setup includes a PHP 8.3-FPM application container, an Nginx web server, and a MariaDB 12 database, all orchestrated via docker-compose. The configuration provides pre-configured environment variables for WordPress/Bedrock, including database credentials and security salts, and exposes the application on port 8080.
.devcontainer · high confidence
Initial project scaffolding and configuration
This change establishes the foundational structure for the Bedrock WordPress boilerplate. It introduces essential configuration files including \.editorconfig\ for consistent coding standards, \pint.json\ for PHP code formatting, and \wp-cli.yml\ to define the web root and WordPress path. The \.env.example\ file is expanded to support environment variables for database credentials, WordPress URLs, debug logging, and security salts, while also introducing support for DSN-based database connections. The \.gitignore\ is updated to reflect the new folder structure (e.g., \web/wp\, \web/app\), and \phpunit.xml.dist\ is added to configure the test suite. Additionally, the repository includes a \LICENSE.md\, \.gitattributes\ for export exclusions, and removes legacy files such as \Capfile\, \index.php\, and the old \CHANGELOG.md\ and \CONTRIBUTING.md\.
(repo-wide) · high confidence
Introduce Bedrock Autoloader mu-plugin and restructure web directory
This change introduces the Bedrock Autoloader as a new must-use plugin (mu-plugin) located at web/app/mu-plugins/bedrock-autoloader.php, which automatically loads standard plugins during the mu-plugin loading phase to simplify plugin management. Additionally, the project structure is reorganized by moving the plugins, themes, and uploads directories from the root app/vendor folders into the new web/app hierarchy, aligning with the standard Bedrock web root layout.
web/app · high confidence
Behavioural changes
Major configuration overhaul with Dotenv v5 and new environment handling
The configuration system has been significantly restructured: the Capistrano deploy script has been removed, and application.php now uses Dotenv v5 with an immutable repository to load .env and optional .env.local files only if they exist. Environment detection defaults to production instead of development, and WP\_ENVIRONMENT\_TYPE is now automatically derived from WP\_ENV for standard environments. Database configuration now supports SSL via DB\_SSL, optional DB\_PREFIX, and DATABASE\_URL parsing, with DB\_CHARSET defaulting to utf8mb4. Security and debugging settings have been updated to disable file editing and modifications by default, allow disabling WP\_CRON via environment variable, enable WP\_DEBUG\_LOG optionally, and improve HTTPS detection behind reverse proxies.
config · high confidence
Refactor environment configuration to use Roots WPConfig and adjust development settings
The environment-specific configuration files (development, staging, production) have been refactored to use the \Roots\\WPConfig\\Config\ class instead of direct \define()\ calls, improving consistency and maintainability. In the development environment, fatal error handling is now disabled (\WP\_DISABLE\_FATAL\_ERROR\_HANDLER\), error display is explicitly enabled, and debug logging defaults to true via the \WP\_DEBUG\_LOG\ environment variable. The production environment configuration file has been removed, implying that production settings are now managed elsewhere or default to standard WordPress behavior, while staging retains indexing restrictions.
config/environments · high confidence
Removal of custom theme directory registration
The custom mu-plugin that explicitly registered the WordPress themes directory has been removed. This means the site no longer relies on this specific manual registration step for theme discovery, reverting to default WordPress theme loading behavior.
app/mu-plugins · high confidence
Removal of local Capistrano deployment configurations
The local Capistrano deployment configuration files for the production and staging environments have been removed from the repository. This change eliminates the in-repo server definitions and SSH settings, indicating that deployment configuration has been migrated to an external repository or management system.
config/deploy · high confidence
Restructure web root and update autoload paths
The application's web root has been moved into a dedicated \web/\ directory. The \wp-config.php\ file has been relocated to this new directory, and its internal paths for \vendor/autoload.php\ and \config/application.php\ have been updated to use \dirname(\_\DIR\\_)\ to correctly resolve the parent directory from the new location. A new \web/index.php\ entry point has been added to bootstrap the WordPress view.
web · high confidence
Test coverage
Added Pest testing scaffold
Added a basic test setup using the Pest testing framework, including a configuration file (tests/Pest.php) and a placeholder feature test (tests/Feature/ExampleTest.php) that verifies a simple assertion.
tests · high confidence
Dependencies
Major dependency overhaul and removal of Ruby deployment tooling
This change removes the Ruby-based Capistrano deployment configuration (Gemfile and Gemfile.lock) and replaces the legacy Composer setup with a modernized \composer.json\. The project now requires PHP 8.3, uses \roots/wordpress\ v7.1.2 instead of the previous WordPress 3.8 package, and switches from \vlucas/phpdotenv\ to \oscarotero/env\ for environment variable management. Additionally, it introduces \roots/bedrock-autoloader\, \roots/bedrock-disallow-indexing\, and \roots/wp-config\, updates installer paths to the \web/\ directory structure, and adds development dependencies for \laravel/pint\ and \pestphp/pest\ for code linting and testing.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 51.1 → 50.5 (-0.6)
- Rubric changed (rubric-2026.11.2 → rubric-2026.11.4) — scores are not directly comparable.
Lenses
- Code Health 65.4 → 54.3 (-11.1)
- Architecture 69.0 → 69.0 (0.0)
- Maturity 50.3 → 54.4 (+4.1)
- Readiness 42.5 → 42.5 (0.0)
- Security 69.6 → 69.6 (0.0)
Resolved (1)
- No ADRs found
New (1)
- No ADRs found (composer.json)
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
roots/bedrock was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 17 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 4a8b67f7c0553e96186b60d31b10399f56d5a47a — the exact code this score is about.
- Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.84+preprod-d645ca9bbedd.