gmazzap/raph

Clear licensing, a readable README, and a small dependency surface help adoption. The project has no recent security tooling and its lone maintainer provides little evidence of current support.

Latest 0.3.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has six releases, but its latest release was over 11 years ago and there have been no releases in the last 12 months. That is strong evidence of abandonment for a WordPress plugin.

Repo commit activity

The repository has had zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for over 11 years.

Maintainers

One registry maintainer is consistent with a small user-owned project, but it provides limited visible publishing capacity when the project has also been inactive for over 11 years.

Project backing

The registry namespace and repository are owned by the same individual user, providing direct ownership alignment but no organizational backing to offset the thin maintenance capacity.

Repo issue activity

There are no open issues or pull requests, avoiding an unresolved backlog. The absence of recent issue activity does not compensate for the lack of releases and commits.