bugban/laravel

This is a usable but very young package with encouraging recent activity: it has 11 stable releases over 55 days, 17 commits in the last 3 months from two active contributors, an unarchived repository, and a clear MIT declaration. However, the package has no tests or changelog in either the artifact or repository, no security scanning or security policy, and no community adoption indicated by repository stars or forks. The small eight-file codebase and rapid release cadence warrant some caution for production adoption, despite the absence of deprecation and install-time lifecycle scripts.

Latest v1.7.1

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The artifact and repository contain the same small eight-file tree, making the published contents transparent and consistent, but the limited scaffolding provides little evidence of broader validation.

Package scaffolding

A substantive README is present, but neither the package artifact nor repository contains tests or a changelog. For a young integration package, this is a meaningful maintenance and transparency gap.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational maintenance handoff signal. This is not inherently unhealthy, but it leaves the small maintainer base more consequential.

Release history

The package is only 55 days old, but it has already had 11 releases, including releases within the last day. This demonstrates active iteration while leaving limited evidence of long-term stability.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. This is not inherently negative for a small package, but it provides no evidence of user-driven maintenance or review.