oasis/logging

Healthy and reasonable to adopt. It has a long history, seven releases in the last year, a current stable release, clear licensing, tests, documentation, and organizational backing; the main caveats are very low repository activity and no documented security policy.

Latest v3.1.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a limited publishing base. However, the repository is owned by an organization, so the short registry maintainer list is not by itself strong evidence of project abandonment.

Repo commit activity

There were no commits and no active maintainers during the last three months. Although the repository was recently pushed and the registry shows seven releases in the last year, the current source-level activity is thin.

Repo popularity

The repository has zero stars, one fork, and three watchers, indicating little visible community adoption. Popularity is supporting evidence rather than a decisive health measure, especially given the package's release history.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The build setup is appropriate, while security-process visibility is limited.

Security policy

The repository has no documented security policy. This is a transparency gap for reporting vulnerabilities, but it is not severe enough to outweigh the package's release history and organizational backing.