lithemod/hash

Clear documentation, tests, licensing, and a minimal dependency profile reduce adoption friction. The small project has little operational and security-process evidence, so future fixes and review capacity are uncertain.

Latest v1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published nearly two years ago, with no releases in the last 12 months. That limits evidence of ongoing maintenance, although the package is not deprecated.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the repository last being pushed nearly two years ago. This is meaningful abandonment risk, though not enough by itself to make the package unfit.

Repo tooling

Composer is used for the build, but no security-scanning tooling is reported. For a password-hashing package, that is a modest transparency and maintenance-process gap.

Security policy

The repository has no security policy. That makes vulnerability reporting and coordinated maintenance less clear for a security-sensitive package.

Workflow audit

No GitHub Actions workflows were present, so there are no workflow findings, but there is also no automated workflow evidence to support ongoing testing or release hygiene.