neo3k/laravel-kms-encryption

Release historydanger

This package has only one release, published about four years ago, and none in the last 12 months. The lack of release cadence is a substantial maintenance and compatibility concern.

Project backingcaution

The package and repository are owned by the same individual account rather than an organization. This does not make the release unsafe, but it provides limited evidence of institutional maintenance capacity.

Repo issue activitycaution

There are no open issues or pull requests and no activity in the last month. This is consistent with a quiet project, but does not independently prove abandonment.

Repo popularitycaution

The repository has only 1 star, 1 fork, and 1 watcher. Low interest is supporting evidence of limited maturity, though popularity alone does not determine whether a small package is maintained.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tooling is present. The missing scanning is a modest transparency gap, not a severe dependency risk by itself.