samuelpouzet/crypt

The code is small, licensed, documented, and has no install-time scripts or runtime packages. A single maintainer and no security scanning leave limited ongoing assurance.

Latest 1.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer is responsible for publishing the package. For this small user-owned project that is a limited contributor base and creates some continuity risk.

Project backing

The package is backed by an individual repository owner rather than an organization, so the single-maintainer signal represents a genuinely thin project base.

Release history

The package has only two releases, both in March 2025, with no releases in the last 12 months. This suggests limited evidence of ongoing maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with no releases in the last 12 months, this is meaningful evidence of stalled maintenance.

Repo popularity

The repository has zero stars and forks and one watcher. This offers little external validation, though popularity is supporting evidence rather than a health verdict.