shreesoftech-rupesh/laravel-database-encryption

Release historydanger

Only four releases exist, clustered around the initial publication, and the latest release was about 16 months ago. This suggests the package may be abandoned despite having a stable current version.

Repo commit activitydanger

There were no commits and no active maintainers during the measured three-month period. Combined with the stale latest release, this is strong evidence of inactive maintenance.

Project backingcaution

The repository is owned by a user account rather than an organization, so the small registry maintainer list does not indicate organizational backing. This offers limited assurance of maintenance capacity.

Repo popularitycaution

The repository has one star, no forks, and no watchers. Popularity is not required for health, but this extremely small user base provides little evidence of community validation or support.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest transparency and maintenance gap.