Does Your PHP Package Need Its Own Documentation Site?
When a dedicated docs site pays off for a Laravel package, when a long README is genuinely the better choice, and the signs you've built one too early.
Read guide →Laravel Badge · Field notes
Guides
Practical guides on Laravel package security, tooling, and ecosystem best practices.
12 entries · Newest first
The archive
Section 01 · All guides
Making Your Laravel Package Discoverable on Packagist
Most composer.json files only have enough metadata to install. Here's what keywords, homepage, support, and funding actually do for discovery.
Read guide →Shipping Laravel Boost Guidelines With Your Package
How to add AI guidelines and skills to a package you maintain so Laravel Boost picks them up automatically, and how to add a badge to advertise it.
Read guide →Measuring the Success of Your Laravel Package
Most maintainers obsess over GitHub stars and miss the real signals. Here's what to measure, where to find it, and how to interpret it.
Read guide →Making Your Laravel Package Easier to Contribute To
How maintainers can lower the barrier to contribution — CONTRIBUTING.md, issue labels, local setup, and review habits that turn one-off PRs into a community.
Read guide →How to Contribute to an Open Source Laravel Package
A practical guide to contributing to open source Laravel packages — from finding good first issues and setting up a dev environment to getting your PR merged.
Read guide →Using Composer 2.10 to Help Your Users Stay Secure
Composer 2.10 brings malware filtering and a unified security policy that surfaces CVEs to your users. Here's what package developers should know and do.
Read guide →Releasing a Major Version: Guiding Users from v1 to v2
How to plan, communicate, and ship a breaking v2 for your Laravel package — covering deprecation, upgrade guides, tooling, and supporting both versions.
Read guide →Laravel Package Veteran: A Q&A with Wendell Adriel
Wendell Adriel, Laravel OSS team member, on his new package Laravel Expressive, using AI in development, and what it takes to maintain packages long-term.
Read guide →Securing Your Packagist Account as a Package Developer
Credentials were the entry point in the Laravel-Lang supply chain attack. Steps to take on Packagist and GitHub to protect your packages and their users.
Read guide →Setting Up GitHub Actions CI for Your Laravel Package
How to set up CI for your Laravel package: multiple PHP and Laravel versions, minimum dependencies, cross-platform runs, and test matrices.
Read guide →Securing Your Laravel Packages with Laravel Moat
Laravel Moat is a new tool from Nuno Maduro that audits your GitHub organisation's security posture. Here's why you should run it on your packages today.
Read guide →Put a badge on your package
Section 02 · Make it yours
Dynamic SVG badges, generated from Packagist in seconds.
Generate a badge →