maymeow/cryptography

The repository has tests, a changelog, release notes, and a clear MIT license. Its single registry release dates from October 2021, while recent repository activity has not produced a new release; all six workflow actions are unpinned and no security policy is present.

Latest v1.0.0

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only one release exists, dated October 2021, with no releases in the last 12 months. This is a meaningful maintenance and adoption risk despite the repository having a later push.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, which is concerning for a cryptography library even though it is not archived.

Project backing

The package and repository are owned by the same individual account, so the source linkage is coherent, but there is no organization backing shown to broaden maintenance capacity.

Repo issue activity

There are four open issues and one open pull request, with no issues or pull requests created or merged in the last month, suggesting limited visible maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap for security-sensitive code.