Package Health/claudiodekker/laravel-auth-bladebones

claudiodekker/laravel-auth-bladebones

Risky to adopt for a new project: the package has had no release in about 3 years and 5 months, with no recent repository commits. Tests, a license, and an unarchived repository help, but missing documentation and limited security-maintenance evidence increase abandonment risk.

Latest v0.2.0

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published about 3 years and 5 months ago, and there were no releases in the last 12 months. The short release history provides little evidence of ongoing maintenance.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the long release gap, this is strong evidence that maintenance has stalled.

Dangerous workflows

The repository has one pull_request_target workflow. No untrusted checkouts or script injection were detected, but this workflow type still warrants review because it can run with elevated repository context.

Package scaffolding

The package contains no README, which makes integration harder for a library, although repository and package tests are present and provide some compensating project evidence.

Project backing

The repository is owned by an individual account rather than an organization. This does not establish poor health, but it provides less visible institutional backing for a package already showing stalled activity.