exe/cloak

Release historydanger

The package has had only 3 releases, all clustered around July 2025, with no releases in the last 12 months despite being about 416 days old. This is a meaningful maintenance concern for a low-level TLS client.

Repo commit activitydanger

There were 0 commits and 0 active maintainers in the last 3 months, consistent with the release history showing no releases for over a year. This materially raises abandonment risk.

Project backingcaution

The repository is owned by an individual rather than an organization, and no organizational backing is shown. Combined with zero recent commit activity, this leaves limited visible maintenance capacity.

Repo toolingcaution

Composer is used as a build tool, but no security scanning tools are configured. For code implementing TLS and HTTP protocol behavior, that is a genuine validation gap.

Security policycaution

The repository has no security policy. That weakens transparency around reporting and handling vulnerabilities in a security-sensitive client.