vjroby/laravel-pbkdf2

Release historydanger

The latest release was published in April 2015, and there have been no releases in roughly 11 years. This is strong evidence of abandonment risk despite the package not being formally deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push in April 2015. The long-standing lack of activity materially lowers maintenance confidence.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 1 watcher, providing little evidence of a broad community that could help sustain or review the package.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. This is a transparency and maintenance gap, though it is less significant than the package's prolonged inactivity.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. That matters for a cryptographic package, even though this alone does not make the release unfit.