arzzen/php-time-lock-encryption

Release historydanger

The package has only one release, published over 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment despite the stable version label.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, and its last push was over six years ago. This substantially weakens confidence in ongoing maintenance.

Maintainerscaution

Only one registry account has publishing access. This is a modest resilience concern for an independently owned project, though registry access alone does not establish actual maintenance activity.

Security policycaution

The repository has no security policy. For a cryptography-focused library, this removes a useful channel for reporting and handling security issues.