Package Health/code-distortion/clarity-logger

code-distortion/clarity-logger

The package is well documented, licensed, tested in its repository, and has a focused dependency set. Missing security scanning, an absent security policy, and four unpinned workflow actions reduce confidence in its maintenance hygiene.

Latest 0.1.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published 993 days ago, with no releases in the last 12 months. That is meaningful abandonment risk for a package intended as a Laravel dependency.

Repo commit activity

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

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is neutral when there is no reported backlog, but it does not demonstrate active maintenance.

Repo popularity

The repository has no stars or forks and one watcher. This provides little supporting evidence of adoption, but popularity is not decisive for a small package.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a maintenance-hygiene gap rather than evidence that the package is unsafe.