starlit/db-logging

Clear documentation, tests, release notes, and licensing make the package transparent. Its only release was over seven years ago, with no recent commits or active maintainers, so dependency risk is substantial.

Latest 1.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one release, on 2019-03-18, and no releases in the last 12 months. With the package now over seven years old, this is strong evidence of abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the last release being over seven years ago, this materially increases abandonment risk.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull request activity. While this avoids an unresolved queue, it also gives no evidence of active maintenance.

Repo popularity

The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these numbers provide little evidence of a broad support community.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. The missing scanner is a modest hygiene gap and is less important than the long-term inactivity.