Maintainers

There is no CODEOWNERS file in this repository — ownership is implicit and concentrated. The table below uses git history to surface the people who actually touch each part of the skeleton.

Bot accounts (github-actions[bot], etc.) are excluded. Counts cover the default branch (13.x) over the ~15-year project history; "Recent contributors" focuses on activity since 2025-01-01.

Skeleton-wide

Subsystem	Lifetime top contributors	Recent (since 2025-01-01)
Skeleton	Taylor Otwell (4,649), Dries Vints (358), Graham Campbell (127), Dayle Rees (106)	Taylor Otwell, Nuno Maduro, Wendell Adriel, community PR authors

Per-subsystem activity

These rows reflect commits to each path since 2025-01-01.

Subsystem (path)	Top recent committers
app/	Taylor Otwell, Nuno Maduro
bootstrap/	Taylor Otwell
config/	Taylor Otwell, Ahmed Alaa, Mior Muhammad Zaki
database/	Taylor Otwell, Jack Bayliss, Nuno Maduro
routes/	Taylor Otwell
resources/	Taylor Otwell, Wendell Adriel (recent Vite-fonts PR #6806)
tests/	(no commits since 2025-01-01 — tests/ is unusually static)
public/	(no recent activity)
storage/	(structural-only; no recent activity)
.github/workflows/	Taylor Otwell
composer.json	Taylor Otwell, Nuno Maduro, Jesper Noordsij
package.json, vite.config.js	Wendell Adriel, Taylor Otwell, robinmiau
.npmrc	Wendell Adriel (371cc0b8), Leo Yanes (9d195133)
.gitignore	Various — accumulates AI-tool ignores

Project leadership

Role	Person
Project lead / BDFL	Taylor Otwell
Security contact	Taylor Otwell (taylor@laravel.com) — per README.md
Frequent core contributors	Nuno Maduro, Dries Vints (historical), Jack Bayliss, Wendell Adriel

The repository's .github/workflows/issues.yml and .github/workflows/pull-requests.yml delegate to the org-level laravel/.github repo, which is where the merge policy and triage automation actually live. The PRs that touch these workflow files are typically mass-applied via reusable-workflow updates in laravel/.github, not edited here.

Where to ask questions

• Bug reports / feature requests — open an issue against laravel/laravel on GitHub. Issues that affect the framework (not just the skeleton) are usually redirected to laravel/framework.
• Security disclosures — email Taylor directly per the README.
• General discussion — Laracasts forums, Laravel Discord, or r/laravel on Reddit. The maintainers don't usually answer general usage questions on the issue tracker.

How to find the right person on a specific change

git log --since="2024-01-01" --pretty=format:"%an" -- <path-or-file> | sort | uniq -c | sort -rn | head -5

That command, scoped to the file or directory you're touching, gives you the names with the most recent context. It's not a substitute for opening a PR and letting review happen organically, but it's useful when you want to ping a specific reviewer for a tricky change.