hyperf-ext/encryption

Usable with caveats: the package is clearly backed by a matching organization repository, has a consumer README, tests in source, and no deprecation or dangerous workflow findings. However, the registry has had no release in about 4 years and 6 months, while repository activity evidence is limited and workflow permissions are unspecified.

Latest v2.2.1

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest registry release was published about 4 years and 6 months ago, with no releases in the last 12 months. This is a meaningful maintenance concern, although the repository was pushed more recently.

Repo issue activity

There are no new or closed issues in the last month and no merged pull requests, with one pull request still open. This indicates limited recent visible development activity.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. The missing scanning is a transparency gap, though it is not by itself evidence that the package is unsafe.

Security policy

The repository has no security policy. For an encryption component, the absence of a documented vulnerability-reporting path is a genuine transparency and maintenance gap.

Token permissions

Both workflows omit top-level token permissions, so their required access is not explicitly constrained at the workflow level. No workflow requests top-level write access, which limits the severity of this gap.