carnage/doctrine-encrypted-column

Release historydanger

The package has only two releases, with the latest published nearly nine years ago and none in the last 12 months. That long release gap is a substantial maintenance and compatibility concern for an encryption library.

Repo commit activitydanger

The repository recorded no commits and no active maintainers during the last three months, consistent with the nearly nine-year gap since the latest release. This strongly increases abandonment risk.

Maintainerscaution

Only one registry account can publish the package, which leaves little publishing redundancy. The matching repository and its lack of recent activity reinforce the concern rather than compensate for it.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance gap for a security-sensitive dependency, although the repository does contain tests.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is especially relevant for a package whose stated function is encryption.