paragonie/eloquent-ciphersweet

Release historycaution

Only one release exists, published about 350 days ago, so there is little release history to demonstrate sustained maintenance. The repository was updated at the time of release, but that does not establish ongoing activity.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months. For a package approaching a year since its only release, this is a concrete maintenance-continuity concern.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a hygiene gap, not evidence of abandonment by itself.

Security policycaution

The repository has no security policy. That weakens vulnerability-reporting transparency for a library providing searchable encryption, although it does not by itself show that the code is unsafe.

Version stabilitycaution

v0.1.0 is an early, non-stable-major release, which signals a less mature compatibility promise. It is not marked as a prerelease, so this is a moderate maturity concern rather than a release warning.