Package Health/aaronsaray/phproblemlogger

aaronsaray/phproblemlogger

Clear documentation, tests, and a matching MIT license make adoption easier. The small dependency surface and absence of install scripts reduce operational risk, while the lack of security tooling or policy leaves maintenance practices thin.

Latest 1.1.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about 10 years ago, with no releases in the last 12 months. Four releases arrived early in the project's life, but this long silence is a substantial abandonment concern.

Repo commit activity

The repository has recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the package's decade-long release silence and indicating no observed ongoing maintenance.

Maintainers

Only one registry account has publishing access. That is a thin publishing base for a user-owned project and increases continuity risk, although access records alone do not establish whether the maintainer is active.

Repo tooling

Composer is used for build and dependency management, which supports reproducible project structure, but no security-scanning tools are present. The missing scanning is a modest hygiene gap rather than evidence of immediate danger.

Security policy

The repository has no security policy. This reduces transparency about vulnerability reporting and handling, especially for a library that processes application errors and runtime information.