lana/logger

The MIT license, README, tests, and single runtime dependency make the package straightforward to inspect and integrate. It has no security policy or scanning, while its one-person project shows no activity for about four years. Pin this only when maintaining the package yourself is acceptable.

Latest 1.0.0

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published about four years ago, with no releases in the last 12 months. That sharply increases abandonment risk despite the stable 1.0.0 version.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for about four years.

Repo popularity

One star and no forks provide little community evidence or backup if the maintainer stops responding. Low popularity alone is not decisive for a small package.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a hygiene gap that adds uncertainty to an already inactive project.

Security policy

The repository has no security policy, leaving no documented path for reporting vulnerabilities or communicating fixes.