</>PackageGraphPackageGraph

laravel/framework

Packagistvv12.69.2

The Laravel Framework.

Not recommended for new projects

No — laravel/framework should not be adopted for new projects. Pulls in 40 transitive packages (at least — some of the tree is still being crawled). No license declared — you have no explicit right to use this code.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • AMaintenance: grade A, Excellent.

    Last published 1 days ago. 50 releases in the last 2 years.

  • CWeight: grade C, Fair — worth a look.

    Pulls in 40 transitive packages (at least — some of the tree is still being crawled).

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • FLicense: grade F, Failing.

    No license declared — you have no explicit right to use this code.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding laravel/framework to a project.

38
Direct dependencies

Runtime packages this one declares itself.

40
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

2
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

MIT

Every license you inherit by installing laravel/framework, not just its own. Check this before a legal review, not after.

Compatibility

PHP
No constraint declared

laravel/framework vs the alternatives

Packages solving a similar problem in the packagist ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
laravel/frameworkthis page001 day ago
laravel/serializable-closure01MIT1 day ago
fruitcake/php-cors01MIT1 day ago

Dependencies

Declared by laravel/framework vv12.69.2. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (38)

brick/math ^0.11|^0.12|^0.13|^0.14composer-runtime-api ^2.2doctrine/inflector ^2.0.5dragonmantank/cron-expression ^3.4egulias/email-validator ^3.2.1|^4.0fruitcake/php-cors ^1.3guzzlehttp/guzzle ^7.8.2guzzlehttp/uri-template ^1.0laravel/prompts ^0.3.0laravel/serializable-closure ^1.3|^2.0league/commonmark ^2.8.1league/flysystem ^3.25.1league/flysystem-local ^3.25.1league/uri ^7.5.1monolog/monolog ^3.0nesbot/carbon ^3.8.4nunomaduro/termwind ^2.0psr/container ^1.1.1|^2.0.1psr/log ^1.0|^2.0|^3.0psr/simple-cache ^1.0|^2.0|^3.0ramsey/uuid ^4.7symfony/console ^7.2.0symfony/error-handler ^7.2.0symfony/finder ^7.2.0symfony/http-foundation ^7.2.0symfony/http-kernel ^7.2.0symfony/mailer ^7.2.0symfony/mime ^7.2.0symfony/polyfill-php83 ^1.33symfony/polyfill-php84 ^1.34symfony/polyfill-php85 ^1.34symfony/process ^7.2.0symfony/routing ^7.2.0symfony/uid ^7.2.0symfony/var-dumper ^7.2.0tijsverkoyen/css-to-inline-styles ^2.2.5vlucas/phpdotenv ^5.6.1voku/portable-ascii ^2.0.2

Relationship graph

Dependencies (left) and dependents (right) of laravel/framework.

Release history

50 releases in the last two years, typically about 0 days apart.

Recent versions of laravel/framework
VersionPublishedLicense
v12.69.2latest1 day ago
v13.31.01 day agoMIT
v13.30.18 days ago
v12.69.18 days ago
v12.69.08 days ago
v13.30.08 days ago
v13.29.015 days ago
v13.28.015 days ago
v11.56.115 days ago
v12.68.015 days ago
v13.27.015 days ago
v11.56.020 days ago
v13.26.122 days ago
v12.67.022 days ago
v13.26.022 days ago

Overview

laravel/framework is an Packagist package that the Laravel Framework. The latest version is v12.69.2.

Who should use it

Teams working in the Packagist ecosystem who need the Laravel Framework and value a focused solution.

When not to use it

Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your Packagist stack.

Pros

  • Actively published to the registry.

Cons

  • Large dependency tree (38 direct dependencies) increases install size and audit surface.
  • No license detected — review usage terms before adopting.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use laravel/framework?

No — laravel/framework should not be adopted for new projects. Pulls in 40 transitive packages (at least — some of the tree is still being crawled). No license declared — you have no explicit right to use this code.

How do I install laravel/framework?

Run `composer require laravel/framework` to add laravel/framework to your Packagist project.

How many dependencies does laravel/framework have?

laravel/framework declares 38 direct dependencies and pulls in 40 packages in total once its runtime tree is resolved.

What license is laravel/framework released under?

No license was detected in laravel/framework's metadata; review the repository before use.

Is laravel/framework still maintained?

The most recent release of laravel/framework (vv12.69.2) was published 1 day ago.