soumik/libcipher

The repository has no security policy or automated security scanning, while its tiny footprint offers little evidence of ongoing review. A valid license and README help, but maintenance evidence is too thin for a dependable dependency.

Latest 1.0

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published over five years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project that has received no maintenance since its initial release.

Project backing

The repository is owned by an individual user rather than an organization, and no organizational backing is shown. Combined with the inactive release and commit history, this provides limited maintenance capacity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counters provide little supporting evidence of community review or adoption.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a small cryptography-related library, that is a meaningful transparency and maintenance gap.