kozo/cryptenv

Usable with caveats: the package is clearly tied to a matching repository, includes tests and documentation, and has no deprecation or unsafe workflow findings. However, it has had no recent commit activity, only two releases clustered on one day, and lacks security-policy and workflow permission hardening.

Latest 0.2

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was about 11 months ago. For an encryption-related plugin, this materially raises maintenance and abandonment concerns.

Project backing

The registry namespace and repository are both owned by the same individual account, providing direct ownership alignment. It does not establish a broader maintainer organization, so the single-person project remains dependent on that owner.

Release history

There were only two releases, both published about 1 hour and 41 minutes apart, with no later release during the package's roughly 342-day lifetime. This suggests limited demonstrated release continuity.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. The clean queue is positive, but the absence of activity provides little evidence of ongoing community review.

Repo popularity

The repository has zero stars, forks, and watchers. This is supporting evidence of a very small user base, but popularity alone is not enough to make the package unsafe.