Nº 01
Laravel Version Compatibility
Reads your package's Composer constraints and renders the Laravel versions it supports. The flagship badge — and the reason this service exists.
Generate this badge →Default
Flat
For the badge
Dynamic SVG badge service · Free · Open source · Packagist-powered
Badges for your Laravel packages
Dynamic SVG badges that detect Laravel version compatibility directly from Packagist. Show supported versions at a glance in your README.
nunomaduro/laravel-sluggable · scale 2:1, 1:1 · SVG
The badges
Section 01 · Six types · Three styles each
Nº 02
Laravel Contributor
For your GitHub profile README — proves you've had a pull request merged into the Laravel framework, skeleton, or documentation.
Generate this badge →Default
Flat
For the badge
Nº 03
Laravel Boost
Show that your project ships with the Laravel Boost AI skill. Styled to match the Boost brand.
Generate this badge →Default
Flat
For the badge
Nº 04
Livewire Version Compatibility
Shows which Livewire versions your package supports, resolved from its Composer constraint.
Generate this badge →Default
Flat
For the badge
Nº 05
Inertia Version Compatibility
Shows which Inertia versions your package supports, resolved from its Composer constraint.
Generate this badge →Default
Flat
For the badge
Nº 06
Filament Version Compatibility
Shows which Filament versions your package supports, resolved from its Composer constraint.
Generate this badge →Default
Flat
For the badge
Nº 07
Reserved
More badges coming soon. Follow @peterfox on 𝕏 to hear about new badges first.
How it works
Section 02 · The process
Step 01
Enter a package name
Type any public Packagist vendor/package into the generator above.
Step 02
We parse the requirements
Package metadata is fetched from Packagist and Laravel or Illuminate version constraints are resolved automatically. Responses are cached for 24 hours.
Step 03
Copy to your README
Get a dynamic SVG badge URL with copy-ready Markdown and HTML snippets for your repository README or package page.
Frequently asked questions
Section 03 · Questions
Want to go deeper? Read our guides on Laravel package development — security, tooling, and ecosystem best practices.
Who is the contributor badge for?
Anyone who has had a pull request merged into
laravel/framework, laravel/laravel, or laravel/docs. Add it to your GitHub profile README to show your contribution to the Laravel ecosystem.
How does this detect Laravel compatibility?
It reads Packagist metadata for your package, inspects Composer requirements, and converts valid Laravel version constraints into a clear badge label.
Does it support illuminate packages?
Yes. Packages depending on individual
illuminate/* components are fully supported and detected automatically.
Can I use this badge in my GitHub README?
Yes. Generate the preview, then copy the Markdown snippet and paste it into your repository README. The badge is a dynamic SVG served directly — no build step required.
How often does the badge update?
Badge responses are cached for 24 hours. After a new package version is published to Packagist, the badge will reflect the updated compatibility within 24 hours.
Are there different badge styles?
Yes. Three styles are available: Default (with gradient), Flat (no gradient), and For the Badge (larger, bolder). Switch between them on the preview page using the style selector.