bakraj/databasewatcher

Its MIT licensing, documented usage, and matching repository make the package transparent to integrate. The long lack of releases or commits leaves maintenance and compatibility risk high.

Latest 0.2

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in July 2018, with no releases in the last 12 months. This indicates prolonged inactivity despite the repository still being available.

Repo commit activity

The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for years.

Project backing

The repository is owned by an individual account rather than an organization. Combined with one registry maintainer and no recent activity, this provides limited visible maintenance capacity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of community validation.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. The missing scanning is a hygiene weakness, while the long inactivity remains the more important concern.