osflab/crypt

Its small, documented codebase is easy to inspect, and the organization-owned repository and declared license provide useful accountability. The lack of security-specific safeguards increases the burden for a cryptography dependency.

Latest 3.0.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This release is the package’s only release, published about 8 years ago, with no releases in the last 12 months. That strongly indicates abandonment risk despite the stable version.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the unchanged release history and indicating no current maintenance capacity.

Repo issue activity

There were no new or closed issues or pull requests in the last month. With no recent commits, this supports a dormant-project assessment rather than showing active stewardship.

Repo popularity

The repository has 0 stars and forks and only 1 watcher, providing little supporting evidence of community scrutiny or adoption. Popularity is secondary, but it does not offset the maintenance gap.

Repo tooling

Composer is used for builds, which is appropriate, but no security-scanning tooling is present. This is a moderate hygiene gap for software handling cryptographic operations.