erikwang2013/encryption

The project has one active maintainer and all five recent commits come from that person, limiting continuity. It has tests, a security policy, frequent stable releases, and read-only workflow permissions; the two unpinned actions are a minor supply-chain hygiene gap.

Latest v1.4.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so the concentrated maintainer activity represents a genuine single-person continuity risk.

Repo bus factor

One contributor made all five recent commits, creating a real continuity risk for a security-sensitive library; no organizational backing is shown to offset that concentration.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and maintenance gap for a cryptography package.

Workflow audit

The only workflow was fully analyzed, uses read-only permissions, and has no reported audit findings. Both action references are unpinned, which is a minor reproducibility and supply-chain hygiene weakness.