jacknoordhuis/laravel-database-hashing

Release historydanger

The latest release was published in March 2019, over seven years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having three releases overall.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the absence of recent releases. The repository is not archived, but there is no observed recent maintenance to compensate.

Maintainerscaution

Only one registry maintainer is listed, leaving the package dependent on a very small publishing base. This increases continuity risk, although the repository owner and registry maintainer match.

Project backingcaution

The project is owned by an individual rather than an organization. That is not inherently unhealthy, but it provides less organizational continuity to offset the single-maintainer and inactivity concerns.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, while the standard build tooling is appropriate for this package.