object/system-logs

The repository has no security policy or security scanning, and its five-file tree offers little evidence of ongoing engineering. MIT licensing and one runtime dependency reduce adoption friction, but do not offset the limited project capacity.

Latest 1.0.1

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, both in June 2016, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the short initial release interval.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release silence and indicating no visible maintenance capacity.

Package scaffolding

The artifact has no README, tests, or changelog, and the repository reports none either. The missing tests and changelog are normal for published artifacts, but the missing README makes this small library harder to evaluate and adopt.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these values provide no supporting evidence of community usage or oversight.

Repo tooling

Composer is used as a build tool, which is appropriate, but no security scanning tooling was detected. That weakens ongoing assurance for a package with no recent maintenance activity.