debugbird/laravel

Release historydanger

The package is about 19 months old but has only two releases, both published within minutes of each other, with no releases in the last 12 months. This suggests an unproven and inactive release history.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, despite the repository being the apparent source. This is the strongest evidence of current maintenance risk.

Dependency profilecaution

The package has only two runtime dependencies and no development dependencies, keeping its dependency surface small. The lack of development dependencies also leaves little visible testing or maintenance infrastructure.

Project backingcaution

The repository is owned by an individual rather than an organization, so the single registry maintainer does not have clear organizational backing to offset the inactive project evidence.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little external evidence of adoption or review.