Package Health/xmarkclx/silverstripe-easylogger

xmarkclx/silverstripe-easylogger

The README, tests, and small dependency surface make the package straightforward to inspect. Maintenance has effectively stopped, and the release has no license declaration or license file, leaving long-term adoption and reuse concerns.

Latest 1.1.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in April 2016, with no releases in the past 12 months and only three releases overall. This is strong evidence of abandonment risk for a package developers may need to maintain themselves.

Repo commit activity

There were no commits and no active maintainers in the past three months, consistent with a project that has been inactive for years. This materially increases the chance that compatibility issues will remain unresolved.

License

No license is declared, detected, or included in the package or repository. That creates a real legal and reuse barrier rather than a cosmetic metadata gap.

Maintainers

Only one registry account has publish access, and the repository is owned by a user rather than an organization. This indicates a thin operational and succession base, though it does not by itself prove abandonment.

Project backing

The registry namespace and repository owner match, and the owner is an individual user. This supports repository ownership alignment but provides no organizational backing to offset the thin maintainer base.