fr3on/laravel-drift

Clear documentation, tests, licensing, and a matching repository make the package easy to evaluate. Its only release and no commits in the last three months leave maintenance unproven, while all five workflow actions are unpinned.

Latest 0.0.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published 163 days ago, so there is not enough release history to demonstrate sustained maintenance. This is a young project rather than clear abandonment, but its cadence remains unproven.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Because this is also the package's only release, there is little observed evidence of ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The absence of scanning is a hygiene gap, not evidence that the package is unsafe or abandoned.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This lowers transparency modestly but does not by itself make the release unfit to use.

Version stability

Version 0.0.1 is an early, non-stable release, which signals that the API and behavior may still change. The package is not marked as a prerelease, so this is a moderate maturity concern rather than a severe warning.