crypt

Release historydanger

The package has only three releases, with the latest in December 2016 and none in nearly 10 years. This strongly raises abandonment risk despite the package's long history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months; its last push was in May 2022, so recent maintenance capacity is not evident.

Maintainerscaution

Only one registry publishing maintainer is listed, leaving a thin release and succession base. The linked repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintainer coverage.

Repo toolingcaution

The repository reports no build tooling and no security scanning. This is a meaningful maintenance and transparency gap for an encryption and hashing utility.

Security policycaution

No security policy is present in the repository, reducing transparency for reporting and handling vulnerabilities in a security-sensitive package.