--- title: The State of Laravel Packages 2026 | daily.dev description: A survey of over 200 Laravel developers reveals strong preferences for using existing packages over building custom solutions (96%), with web search and... canonical: https://daily.dev/posts/the-state-of-laravel-packages-2026-wagypoggh twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The State of Laravel Packages 2026 | daily.dev og:description: A survey of over 200 Laravel developers reveals strong preferences for using existing packages over building custom solutions (96%), with web search and... og:url: https://daily.dev/posts/the-state-of-laravel-packages-2026-wagypoggh og:image: https://api.daily.dev/og/posts/wagypOggH.png og:image:alt: The State of Laravel Packages 2026 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The State of Laravel Packages 2026 **[Daniel Petrica](https://daily.dev/sources/danielpetrica)** · 7 min read · 0 upvotes · 0 comments ## Summary A survey of over 200 Laravel developers reveals strong preferences for using existing packages over building custom solutions (96%), with web search and Packagist as top discovery channels. Update recency and documentation quality rank as the most important selection criteria, while abandoned packages and poor documentation are the community's biggest frustrations. The author used the findings to launch LaraPlugins.io, a new directory for discovering and vetting Laravel packages, including an MCP integration for AI agents. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What do Laravel developers look for most when choosing between similar packages? Recency of updates and maintenance status rank as the top factor, followed by documentation quality, GitHub stars/popularity, and author reputation. A survey of 200+ active Laravel developers found 61% spend just 5-30 minutes vetting a package before running composer require, favoring quickly scannable signals over deep code audits. _Developers weighing package options can browse related discussions and comparisons on daily.dev to vet Laravel tools faster._ ### What are the biggest frustrations Laravel developers have with the package ecosystem? Lack of documentation or usage examples and too many abandoned or outdated packages tie for the top complaint, each cited by around 70% of respondents in a survey of 200+ active Laravel developers. Difficulty comparing similar packages (28%) and uncertainty about Laravel version compatibility (13%) rounded out the top frustrations. _Keep up with Laravel ecosystem pain points and package health discussions by following related coverage on daily.dev._ ## Similar posts on daily.dev - [Dependency Hygiene](https://daily.dev/posts/dependency-hygiene-wk2t5wl36) · stitcher.io · 23 upvotes · 0 comments - [State of Laravel 2026 Survey Is Now Open](https://daily.dev/posts/state-of-laravel-2026-survey-is-now-open-x3zovy2vf) · Laravel News · 5 upvotes · 2 comments --- Tags: [#php](https://daily.dev/tags/php), [#laravel](https://daily.dev/tags/laravel) [View this post on daily.dev](https://daily.dev/posts/the-state-of-laravel-packages-2026-wagypoggh) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The State of Laravel Packages 2026","url":"https://daily.dev/posts/the-state-of-laravel-packages-2026-wagypoggh","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-state-of-laravel-packages-2026-wagypoggh"},"datePublished":"2026-09-29T12:32:29.820Z","dateModified":"2026-09-29T12:33:10.702Z","description":"A survey of over 200 Laravel developers reveals strong preferences for using existing packages over building custom solutions (96%), with web search and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3ab1eaee603ef6671170a64d534e40c4?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3ab1eaee603ef6671170a64d534e40c4?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Daniel Petrica","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Daniel Petrica","logo":"https://media.daily.dev/image/upload/s--jkfwlnJz--/f_auto,q_auto/v1774964393/logos/danielpetrica?_a=BAMAMiWQ0","url":"https://daily.dev/sources/danielpetrica"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-state-of-laravel-packages-2026-wagypoggh","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"php,laravel","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Daniel Petrica","item":"https://daily.dev/sources/danielpetrica"},{"@type":"ListItem","position":3,"name":"The State of Laravel Packages 2026"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-state-of-laravel-packages-2026-wagypoggh#faq","mainEntity":[{"@type":"Question","name":"What do Laravel developers look for most when choosing between similar packages?","acceptedAnswer":{"@type":"Answer","text":"Recency of updates and maintenance status rank as the top factor, followed by documentation quality, GitHub stars/popularity, and author reputation. A survey of 200+ active Laravel developers found 61% spend just 5-30 minutes vetting a package before running composer require, favoring quickly scannable signals over deep code audits. Developers weighing package options can browse related discussions and comparisons on daily.dev to vet Laravel tools faster."}},{"@type":"Question","name":"What are the biggest frustrations Laravel developers have with the package ecosystem?","acceptedAnswer":{"@type":"Answer","text":"Lack of documentation or usage examples and too many abandoned or outdated packages tie for the top complaint, each cited by around 70% of respondents in a survey of 200+ active Laravel developers. Difficulty comparing similar packages (28%) and uncertainty about Laravel version compatibility (13%) rounded out the top frustrations. Keep up with Laravel ecosystem pain points and package health discussions by following related coverage on daily.dev."}}]} ```