Package Health/payamjafari/laravel-db-encrypter

payamjafari/laravel-db-encrypter

The clear MIT license, focused four-file layout, and lack of install scripts make the package straightforward to inspect. Its tiny community and missing security policy provide little reassurance for a package that has not changed in years.

Latest v1.1.1

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made no release in nearly five years: all four releases occurred around its first release on November 21, 2021. That long period without a new release is strong evidence of abandonment risk.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the last push occurring nearly five years ago. This is a substantial abandonment risk for a dependency.

Project backing

The repository is owned by a user account rather than an organization, so there is no visible organizational backing to compensate for the small maintainer base or stalled activity.

Repo popularity

The repository has one star, zero forks, and zero watchers, showing very little independent adoption or community visibility. Popularity is supporting evidence rather than a verdict, but here it reinforces the maintenance concern.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest transparency and maintenance gap rather than proof of a defect.