sevming/crypt

The compact seven-file implementation is easy to inspect, with an MIT license, README, and release note for this version. No tests, security policy, or security scanning are present, increasing uncertainty for cryptographic code.

Latest v1.0.2

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no registry release in nearly eight years, with only three releases overall and none in the last 12 months. This is strong evidence of abandonment for a dependency that may need security and compatibility maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the last push being nearly six years ago, this indicates sustained maintenance inactivity.

Maintainers

Only one registry account has publish access. Because the repository is user-owned and there is no organizational backing shown, this leaves a thin publishing and continuity base.

Project backing

The registry namespace and repository owner are the same individual account, so the source appears to correspond to the package. There is no organization backing shown to compensate for the single-person maintenance base.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. For a cryptographic package, that missing security practice is a meaningful transparency and maintenance concern.