dzone/encryptphp

Its MIT declaration and tiny Composer-only artifact make its licensing and installation shape clear. The repository is unarchived but has no reported security policy or scanning, adding maintenance and transparency concerns.

Latest 1.0

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published nearly 5 years and 10 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the single historical release, this indicates no recent maintenance capacity.

Maintainers

Only one registry account has publish access. Because the repository is user-owned rather than organization-backed, this indicates a thin publishing base and limited apparent continuity.

Package file tree

The artifact and repository each contain only composer.json and one source file. This is a transparent, minimal layout, but it also offers little evidence of testing, documentation, or project maturity.

Project backing

The linked repository is owned by a personal user account, not an organization. With only one registry maintainer and no recent activity, there is little visible institutional backing to reduce abandonment risk.