zfegg/http-content-crypt

Release historydanger

The package has had no registry release in over 9 years, with all 3 releases concentrated in February 2017. This is strong evidence that maintenance has stopped.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and leaving no evidence of current maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap that matters more for middleware handling encrypted content.

Security policycaution

The repository has no security policy, reducing transparency for reporting issues in a package that implements cryptographic content handling. The tested source and clear README provide only limited compensation.